Scripted installation of Nextcloud 28 in iocage jail 2018-03-23

[capio]

You would have created it, in the directory where you placed the script.

Here's your error, and the likely cause. You need to have port 443 on your jail open to the Internet.

allow port forwarding in my router or in free nas settigns? if its freenas settings : how to do

 

[danb35]

allow port forwarding in my router or in free nas settigns?

In your router. Port 80 really should be open too, but Caddy uses 443 to obtain the cert.

 

[capio]

In your router. Port 80 really should be open too, but Caddy uses 443 to obtain the cert.

http://www.portchecktool.com./ says that the port is still closed. but im sure i did right. is it possilbe to change the port to something else? maybe my provider blocks 443 forwarding. i dont know it

 

[danb35]

is it possilbe to change the port to something else?

No, it must be port 443 for Let's Encrypt to reach it. If you're not able to open that port, you can look into DNS validation, or use a self-signed cert instead.

 

[capio]

ok, thanks for your answer. is there a tutorial? dont know how to use a self-signed cert.

 

[danb35]

Re-create the jail, setting SELFSIGNED_CERT=1 in the config file.

 

[capio]

Re-create the jail, setting SELFSIGNED_CERT=1 in the config file.

i did it but still ERR_CONNECTION_REFUSED

cat caddy.log = empty file

 

[danb35]

cat caddy.log = empty file

Is Caddy running in the jail? service caddy status. If it isn't, start it with service caddy start. If you still get the same error, see if there's anything in caddy.log then.

 

[capio]

Is Caddy running in the jail? service caddy status. If it isn't, start it with service caddy start. If you still get the same error, see if there's anything in caddy.log then.

root@nextcloud:/ # service caddy status
caddy is running as pid 79694.

root@nextcloud:/ # cat /var/log/caddy.log -> still no output

 

[capio]

Is Caddy running in the jail? service caddy status. If it isn't, start it with service caddy start. If you still get the same error, see if there's anything in caddy.log then.

i did service caddy restart. now the log looks like:

root@nextcloud:/ # cat /var/log/caddy.log
2019/10/27 03:41:16 [INFO][cache:0xc0001ca370] Started certificate maintenance routine
2019/10/27 03:41:16 [WARNING] Stapling OCSP: no OCSP stapling for [deni2.hopto.org]: no OCSP server specified in certificate
2019/10/27 03:41:16 [INFO] Successfully loaded TLS assets from /usr/local/etc/pki/tls/certs/fullchain.pem and /usr/local/etc/pki/tls/private/privkey.pem
Activating privacy features... done.

Serving HTTP on port 80
http://deni2.hopto.org

2019/10/27 03:41:16 [INFO] Serving http://deni2.hopto.org

Serving HTTPS on port 443
https://deni2.hopto.org

2019/10/27 03:41:16 [INFO] Serving https://deni2.hopto.org
2019/10/27 03:45:14 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: )
2019/10/27 03:45:14 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: http://192.168.178.199/)
2019/10/27 03:46:33 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: )
2019/10/27 03:46:41 http: TLS handshake error from 192.168.178.74:61996: no certificate available for ''
2019/10/27 03:46:43 http: TLS handshake error from 192.168.178.74:61997: no certificate available for ''
2019/10/27 03:46:44 http: TLS handshake error from 192.168.178.74:61998: no certificate available for ''
2019/10/27 03:46:45 http: TLS handshake error from 192.168.178.74:61999: no certificate available for ''
2019/10/27 03:46:46 http: TLS handshake error from 192.168.178.74:62000: no certificate available for ''
2019/10/27 03:46:47 http: TLS handshake error from 192.168.178.74:62001: no certificate available for ''
2019/10/27 03:46:48 http: TLS handshake error from 192.168.178.74:62002: no certificate available for ''
2019/10/27 03:46:54 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: )
2019/10/27 03:49:12 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: )
2019/10/27 03:49:15 [INFO] 192.168.178.199 - No such site at :80 (Remote: 192.168.178.74, Referer: )
2019/10/27 04:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 04:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 05:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 05:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 06:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 06:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 07:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 07:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 08:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 08:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 09:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 09:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 10:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 10:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 11:41:16 [INFO][cache:0xc0001ca370] Scanning for stale OCSP staples
2019/10/27 11:41:16 [INFO][cache:0xc0001ca370] Done checking OCSP staples
2019/10/27 12:32:17 [INFO] SIGTERM: Shutting down servers then terminating
2019/10/27 12:32:17 [INFO][cache:0xc0001ca370] Stopped certificate maintenance routine

 

[Thomas_VDB]

Hi,
Been using scripted nextcloud on my freenas hapilly for a few months now. Mostly via web-interface to see/download files.
Now I have installed the nextcloud client for windows on my laptop, and everything is syncing ok. However I am not allowed to edit/upload files. No permissions error in nextcloud client. Been googling but as I am no freebsd nor Linux expert, it's difficult to debug this problem. Can someone please advise? Thx!

Up?

 

[Ceetan]

I've been using an installation created by this script for a while now and it's mostly been running smoothly but now I hit a snag.
Two questions:

1.
Even though I'm logged in as an admin the admin button doesn't appear in the upper right drop-down menu. That's not working as intended is it?

2
I was recently prompted to upgrade from nc 14 to nc 15 and so I did. Nothing seems not to be working except the above-mentioned problem but didn't work before hand either. I got the impression that there should be version 16 and even 17 available, but I'm not prompted to upgrade to those. I'm wondering why that is?

 

[danb35]

the admin button doesn't appear in the upper right drop-down menu.

At least in more recent versions, the menu item would be "settings", the same as for a non-admin user, you'd just have more settings available. If you got a prompt to upgrade, you're likely fine.

I got the impression that there should be version 16 and even 17 available

It doesn't look like 17 is available through the built-in updater yet, but I'd expect 16 should be. If you just did the upgrade to 15, it might take a little while for 16 to show up.

 

[capio]

At least in more recent versions, the menu item would be "settings", the same as for a non-admin user, you'd just have more settings available. If you got a prompt to upgrade, you're likely fine.

It doesn't look like 17 is available through the built-in updater yet, but I'd expect 16 should be. If you just did the upgrade to 15, it might take a little while for 16 to show up.

do you know have to fix my issue? i dont find a solution in the internet

 

[danb35]

do you know have to fix my issue?

Aside from your issue having nothing at all to do with what you quoted, you say you've restarted Caddy, and there's now information in the log file. From what I see, it looks like it should be OK. Can you now pull up your site?

 

[capio]

Aside from your issue having nothing at all to do with what you quoted, you say you've restarted Caddy, and there's now information in the log file. From what I see, it looks like it should be OK. Can you now pull up your site?

still ERR_CONNECTION_REFUSED

 

[capio]

192.168.178.251 sent an invalid response.

• Try running Windows Network Diagnostics.

ERR_SSL_PROTOCOL_ERROR

---------------------
Serving HTTP on port 80

http://deni2.hopto.org

2019/11/01 02:13:10 [INFO] Serving http://deni2.hopto.org

Serving HTTPS on port 443

https://deni2.hopto.org

-------------------------

​

�

Service Name	Port Range	Local IP	Local Port	Protocol	Add / Delete
Port Forwarding List (Max Limit : 32)
				TCP UDP BOTH

1	80	192.168.178.251	80	TCP
2	443	192.168.178.251	443	TCP

-----------------------------

This site can’t be reached
deni2.hopto.org took too long to respond.


Try:

• Checking the connection
• Checking the proxy and the firewall
• Running Windows Network Diagnostics

ERR_CONNECTION_TIMED_OUT

--------------------
nslookup:

> deni2.hopto.org
Server: deniz-BHYVE
Address: 192.168.178.84

Non-authoritative answer:
Name: deni2.hopto.org
Addresses: 2003:c6:a733:700:1dc5:5758:c965:4096
79.198.65.169

------------------------
well, im still not giving up. maybe someone see what i dont see. thanks for help

 

[Elo]

I am running FreeNas 11.2-U6 and have been runing Nextcloud instaled with the Dan35 script for a long time without any trouble. During one of the previous updates my Nextlcoud stoped working .. That is I get HTTP Error 500 -- the page can not be shown.
How can I update the whole Nextcloud instalation and contain user data (IDs, passwords etc) (the data content is safely residing outside the jail) Or any other suggestions.. All mount points seems to be intact as pr the info on the GitHub page.

Note: I did a pkg upgrade with same results

root@nextcloud:/ # mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61 "Connection refused")

Other suggestions are also welcome on how to rectify.

 

[danb35]

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61 "Connection refused")

Let's first start by ensuring that it's running: service mysql-server status. If not, try starting it (service mysql-server start) and see if it runs then.

 

[Elo]

Let's first start by ensuring that it's running: service mysql-server status. If not, try starting it (service mysql-server start) and see if it runs then.

root@nextcloud:/ # service mysql-server start
Starting mysql.
root@nextcloud:/ # service mysql-server status
mysql is not running.

Does not seem that I can start it