Hi there,
I’m trying to get a family instance of Next Cloud moved off of an old Nethserver node onto a clean AIO install. There’s two complications – the existing Next Cloud is still in use and sitting on IP and holding the domain.
Both should be easy to surmount – I can reverse proxy to the replacement server on a temporary domain and then change the domain as described here once the existing server is decommissioned.
However, I’m running into frustrations with the reverse proxy – and yes, I’ve worked through all of the reverse proxy steps multiple times. Clearly I’m missing something, but I can’t figure out what. Here’s what’s happening:
Clean setup of Nextcloud-AIO with reverse proxy:
sudo docker run --init --sig-proxy=false --name nextcloud-aio-mastercontainer --restart always --publish 8080:8080 --env APACHE_PORT=11000 --env APACHE_IP_BINDING=0.0.0.0 --env NEXTCLOUD_DATADIR="/home/cloudData" --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock:ro nextcloud/all-in-one:latest
Visit the AIO container interface on 8080. All is well.
Enter domain for validation.
NOTICE: PHP message: The response of the connection attempt to "<MYURL>" was:
NOTICE: PHP message: Expected was: <CODE>
NOTICE: PHP message: The error message was: Connection timed out after 10002 milliseconds
NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things in order to debug things!
Visit the domain in a browser to confirm I receive the same . I do!
Check on the host: curl <MYURL> to confirm the host also receives the code. It does!
So if I receive the code and the host receives the code, why is the master container timing out?
Here’s a more complete log:
$ sudo docker logs -f nextcloud-aio-mastercontainer
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 994
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[Sat Jul 27 10:29:28.986708 2024] [mpm_event:notice] [pid 137:tid 137] AH00489: Apache/2.4.61 (Unix) OpenSSL/3.3.1 configured -- resuming normal operations
[Sat Jul 27 10:29:28.986747 2024] [core:notice] [pid 137:tid 137] AH00094: Command line: 'httpd -D FOREGROUND'
[27-Jul-2024 10:29:28] NOTICE: fpm is running, pid 146
[27-Jul-2024 10:29:28] NOTICE: ready to handle connections
{"level":"info","ts":1722076169.0029786,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1722076169.0042472,"msg":"adapted config to JSON","adapter":"caddyfile"}
NOTICE: PHP message: The response of the connection attempt to "https://cloud2.coxbros.us:443" was:
NOTICE: PHP message: Expected was: 0c0f0f3b7f9fdd59a127ed8631ebcbda8cf3401b0d69d416
NOTICE: PHP message: The error message was: Connection timed out after 10002 milliseconds
NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things in order to debug things!
NOTICE: PHP message: The response of the connection attempt to "<MYURL>" was:
NOTICE: PHP message: Expected was: <CODE>
NOTICE: PHP message: The error message was: Connection timed out after 10002 milliseconds
NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things in order to debug things!
Oh, madness.