Can't reach web page after remove staging script

[BBBosp]

I went through initial setup and everything went well, tested both locally and remotely, was ready to get the let's encrypt cert, ran the remove staging script as suggested because I used the default jail name, and now I can not reach the web page. I thought I got the known bug because I got the following output:

% sudo iocage fstab -l nextcloud +-------+---------------------------------------------------------------------------------------------------------------------------+ | INDEX | FSTAB ENTRY | +=======+===========================================================================================================================+ | 0 | /mnt/bigdata/portsnap/db /mnt/bigdata/iocage/jails/nextcloud/root/var/db/portsnap nullfs rw 0 0 | +-------+---------------------------------------------------------------------------------------------------------------------------+ | 1 | /mnt/bigdata/db /mnt/bigdata/iocage/jails/nextcloud/root/var/db/mysql nullfs rw 0 0 | +-------+---------------------------------------------------------------------------------------------------------------------------+ | 2 | /mnt/bigdata/files /mnt/bigdata/iocage/jails/nextcloud/root/media/files nullfs rw 0 0 | +-------+---------------------------------------------------------------------------------------------------------------------------+

but after following the bug fix instructions nothing has changed.

[Bosstox]

Hi.

Do you got a solution for this? I got the same issu at 12-6 und 13 Beta.

[BBBosp]

My solution was to forget about having nextcloud in a jail on freenas and make a VM with CentOS 7 and run nextcloud 16. Works like a charm and much higher performance

On Sat, Nov 16, 2019, 5:33 AM Ramiz notifications@github.com wrote:

Hi.

Do you got a solution for this? I got the same issu at 12-6 und 13 Beta.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/74?email_source=notifications&email_token=ACH66CK74JQOPRPXMJB2JBLQT7LALA5CNFSM4JJM44X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHPN2Q#issuecomment-554628842, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH66CL6ZYH6YLO2JWWETSLQT7LALANCNFSM4JJM44XQ .

[The-Jaeger]

I've got the exact same issue.

"Secure Connection Failed" "PR_END_OF_FILE_ERROR" "The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem."

[The-Jaeger]

@bosp1301 I tried to do the same thing with Ubuntu with a 500G zvol but it's only detecting the max size as 110 when adding nextcloud as a network drive anywhere else. Did you run into the same issue or was it flawless?

[BBBosp]

It may be attached to the root partition, not the home partition. Check df

On Sun, Nov 17, 2019, 1:54 PM The-Jaeger notifications@github.com wrote:

@bosp1301 https://github.com/bosp1301 I tried to do the same thing with Ubuntu with a 500G zvol but it's only detecting the max size as 110 when adding nextcloud as a network drive anywhere else. Did you run into the same issue or was it flawless?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/74?email_source=notifications&email_token=ACH66CO24VEGUKNGRTRT6UDQUGOPVA5CNFSM4JJM44X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIUKQA#issuecomment-554779968, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH66CM3IPHMV4T5XZCDRELQUGOPVANCNFSM4JJM44XQ .

[The-Jaeger]

@bosp1301 it is attached to the root partition "/". But besides mounting the whole thing elsewhere how do you fix it? It's the only drive on the system besides loop#.

[BBBosp]

I'm using CentOS right now and removed the entire home partition and expanded the root partition to fill the drive. Make sure to remove the home partition from fstab if you go this route because it won't boot otherwise.

On Sun, Nov 17, 2019, 2:02 PM The-Jaeger notifications@github.com wrote:

@bosp1301 https://github.com/bosp1301 it is attached to the root partition "/". But besides mounting the whole thing elsewhere how do you fix it? It's the only drive on the system besides loop#.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/74?email_source=notifications&email_token=ACH66COTBWLPNCHN5AYRXOTQUGPN7A5CNFSM4JJM44X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIUP6A#issuecomment-554780664, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH66COZOCP2DLJ6TJKEHODQUGPN7ANCNFSM4JJM44XQ .

[The-Jaeger]

@bosp1301 so you did this before installing nextcloud? If I did that right now I'd remove everything since I already have it installed. Also, expand the root partition, what do you mean?

[danb35]

Help me out here--what does the discussion about running Nextcloud in a Linux VM have to do with this script?

[danb35]

The only thing the script should do is remove one line from /usr/local/www/Caddyfile, that line being the one that reads ca https://acme-staging-v02.api.letsencrypt.org/directory. If you're having trouble reaching the Nextcloud web interface after running the remove-staging script, see if that line has been removed from the Caddyfile. If it has, see if Caddy is running (service caddy status); if not, try to start it (service caddy start).

[BBBosp]

Nothing, and I apologize if this is the wrong place to have this discussion with Jaeger, I was just replying with my 2 cents after they asked.

I don't know what went wrong with the script, or my implementation of it more likely,but I scrapped the idea of having it on FreeNAS for my own sanity and management purposes.

I didn't have the knowledge to troubleshoot it in FreeNAS in the time frame I had to work on it.

On Sun, Nov 17, 2019, 2:21 PM danb35 notifications@github.com wrote:

The only thing the script should do is remove one line from /usr/local/www/Caddyfile, that line being the one that reads ca https://acme-staging-v02.api.letsencrypt.org/directory. If you're having trouble reaching the Nextcloud web interface after running the remove-staging script, see if that line has been removed from the Caddyfile. If it has, see if Caddy is running (service caddy status); if not, try to start it (service caddy start).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/74?email_source=notifications&email_token=ACH66CPLCDPIHAZJKHXMVNTQUGRTFA5CNFSM4JJM44X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIU5SA#issuecomment-554782408, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH66CLYRF6EJ6LN2TCJQWDQUGRTFANCNFSM4JJM44XQ .

[The-Jaeger]

@danb35 I've tried to start the caddy service but when loading the page it still responds with "refused to connect" and then when "service caddy status" it states it's not running. After restarting the jail it starts with caddy not running.

Also sorry for discussing irrelevant matters, but it feels like it's impossible to get nextcloud running on Freenas with letsencrypt and I thought it would be another option.

[The-Jaeger]

SOLUTION: In the Caddyfile, remove "tls { }" it should be a line high up on the file that should just be empty brackets after running remove-staging.sh. Removing these brackets and tls has got it working again.

More specifically: nano /usr/local/www/Caddyfile Find those lines with "tls {" and the closing bracket "}" and delete them. Then CTRL+X, press "y" and enter Then restart caddy "service caddy restart" Then run "service caddy status" If you get "caddy is running as pid ####" then it is working and you should be able to access nextcloud at your domain.

[danb35]

Thanks, and that explains why I wasn't able to duplicate the issue--I use DNS validation, and that means that stanza of the Caddyfile wouldn't be empty even after the remove-staging script is run.

Now to see if there's a way to make the appropriate changes to both environments by script...

[The-Jaeger]

I am not proficient at scripting YET, so I wish I could help you. But I can provide you with the configuration I had to reproduce this issue since I ran the script three times isolating variables.

You're an unsung hero for this script, it achieves the impossible. Can't thank you enough. Would love to help in anyway possible. On Nov 17 2019, at 6:34 pm, danb35 notifications@github.com wrote:

Thanks, and that explains why I wasn't able to duplicate the issue--I use DNS validation, and that means that stanza of the Caddyfile wouldn't be empty even after the remove-staging script is run.

Now to see if there's a way to make the appropriate changes to both environments by script... — You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://link.getmailspring.com/link/40CD9321-56B4-44A2-B757-1623251A245F@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fdanb35%2Ffreenas-iocage-nextcloud%2Fissues%2F74%3Femail_source%3Dnotifications%26email_token%3DANO5N6SFA5UWFVOVOIGAGQTQUHIKDA5CNFSM4JJM44X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIZNUI%23issuecomment-554800849&recipient=cmVwbHkrQU5PNU42UkxaUjdYNFE2UDVMUjJRNE4zMzRGMkRFVkJOSEhCNVlSRFZNQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe (https://link.getmailspring.com/link/40CD9321-56B4-44A2-B757-1623251A245F@getmailspring.com/1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANO5N6S34YZOQ5ZKXBGZEPLQUHIKDANCNFSM4JJM44XQ&recipient=cmVwbHkrQU5PNU42UkxaUjdYNFE2UDVMUjJRNE4zMzRGMkRFVkJOSEhCNVlSRFZNQHJlcGx5LmdpdGh1Yi5jb20%3D).

[danb35]

I think my last commit to remove-staging.sh should resolve this issue--rather than remove that line, it simply changes the URL to be the production CA. It's redundant (Caddy will use that URL automatically if it isn't specified), but it avoids the problem with the Caddyfile syntax when there isn't a dns directive in the tls { } stanza.