NEXTCLOUD AIO WITH PROXY : PB during first access at https://[SERVER_IP]:8080

jc-59 · 12. Dezember 2023

Hello,
I followed NEXTCLOUD AIO WITH PROXY guide

When I access to https://[SERVER_IP]:8080 , I have the following error

Proxy Error

The proxy server received an invalid response from an upstream server.

The proxy server could not handle the request

Reason: DNS lookup failure for: localhost

Apache/2.4.58 (Unix) Server at 192.168.1.37 Port 8080

I'm searching since hours without any progress ...
Any hint ?

Code

Trying to fix docker.sock permissions internally...
Creating docker group internally with id 995
.+....+.....................+.....+++++++++++++++++++++++++++++++++++++++++++++*......+...+.+...........+.+..+...+...+.+.....+....+..............+.+......+........+.+.....+.+...+...+...+...........+.+.........+......+...+.....+.......+.....+...+.+.....+......+...+....+..+....+.........+..+....+............+..+.+++++++++++++++++++++++++++++++++++++++++++++*.+...+..........+...............+.........+...+............+..+....+.....+.......+..+.+.................+....+...............+...+...+..+......................+...+..+.............+..+...................+..+............+...+...+.......+.................+.+.....+.......+........+.+.....+.+..+......+.......+...+..............+..........+........+....+........+.......+++++
...........+.+...+...........+....+...+.....+.......+..+.........+++++++++++++++++++++++++++++++++++++++++++++*...+++++++++++++++++++++++++++++++++++++++++++++*.....+............+...+.......+........+......+......+..................+................+......+.........+.....+.+...+..+.+.......................+....+..+.........+....+...+...+..+.........+....+......+...+........+...+....+.....+.+.........+..+.+..+.+............+.........+......+..+.............+........................+.........+..+...........................+.......+........+.......+......+.....+...+.+.....+......+.............+..+.........+...+...............+.+..+.............+......+.....+.........+.+...+..+.........+....+...........................+..................+...+..+.+................................+...+.........+...+...+.+...+...+........+....+..+........................+.+........+..............................+.+..............+...+....+.........+.....+....+++++
-----
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
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
INF ts=1702399161.3201852 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
[Tue Dec 12 16:39:21.818691 2023] [mpm_event:notice] [pid 106:tid 140636202498888] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations
[Tue Dec 12 16:39:21.818767 2023] [core:notice] [pid 106:tid 140636202498888] AH00094: Command line: 'httpd -D FOREGROUND'
[12-Dec-2023 16:39:21] NOTICE: fpm is running, pid 112
[12-Dec-2023 16:39:21] NOTICE: ready to handle connections
INF ts=1702399162.9584458 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399165.159842 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399166.261351 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399168.5083659 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399169.593769 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399171.6911216 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399174.7734778 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399176.8854048 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399177.9729917 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399180.0512474 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
INF ts=1702399183.1499505 msg=using provided configuration config_file=/Caddyfile config_adapter=
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
[Tue Dec 12 16:40:50.187040 2023] [proxy:error] [pid 125:tid 140636192271160] [client 192.168.1.144:54170] AH00898: DNS lookup failure for: localhost returned by /
[Tue Dec 12 16:40:55.302920 2023] [proxy:error] [pid 125:tid 140636191136568] [client 192.168.1.144:54170] AH00898: DNS lookup failure for: localhost returned by /favicon.ico, referer: https://192.168.1.37:8080/
[Tue Dec 12 16:58:25.465817 2023] [proxy:error] [pid 125:tid 140636191566648] [client 192.168.1.144:54949] AH00898: DNS lookup failure for: localhost returned by /
[Tue Dec 12 16:58:30.544355 2023] [proxy:error] [pid 125:tid 140636190849848] [client 192.168.1.144:54949] AH00898: DNS lookup failure for: localhost returned by /favicon.ico, referer: https://192.168.1.37:8080/

Alles anzeigen

chente · 12. Dezember 2023

It looks like Nextcloud is trying to configure Caddy. Have you installed and configured Nginx Proxy Manager as that guide says?

jc-59 · 12. Dezember 2023

Yes, all steps

chente · 12. Dezember 2023

Zitat von jc-59

DNS lookup failure for: localhost

If you have done all the configurations as described, the only thing I can think of that could fail is the domain pointing to your server. You must make sure that this configuration is correct. This site can help https://www.whatsmydns.net/

Then check that IP on your router and make sure it points to your server.

jc-59 · 12. Dezember 2023

I've just followed NEXTCLOUD AIO WITHOUT PROXY guide

Of course i've stopped my nginx container

I have the same issue ...

Code

 -1 }">Trying to fix docker.sock permissions internally...
 -1 }">Creating docker group internally with id 995
 -1 }">Initial startup of Nextcloud All-in-One complete!
 -1 }">You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
 -1 }">E.g. https://internal.ip.of.this.server:8080
 -1 }">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:
 -1 }">https://your-domain-that-points-to-this-server.tld:8443
 -1 }">[Tue Dec 12 19:50:05.977747 2023] [mpm_event:notice] [pid 108:tid 140140975696712] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations
 -1 }">[Tue Dec 12 19:50:05.978351 2023] [core:notice] [pid 108:tid 140140975696712] AH00094: Command line: 'httpd -D FOREGROUND'
 -1 }">INF ts=1702410605.990367 msg=using provided configuration config_file=/Caddyfile config_adapter=
 -1 }">[12-Dec-2023 19:50:05] NOTICE: fpm is running, pid 113
 -1 }">[12-Dec-2023 19:50:05] NOTICE: ready to handle connections
 -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
 -1 }">INF ts=1702410608.296198 msg=using provided configuration config_file=/Caddyfile config_adapter=
 -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
 -1 }">INF ts=1702410610.3765018 msg=using provided configuration config_file=/Caddyfile config_adapter=
 -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
 -1 }">INF ts=1702410612.459268 msg=using provided configuration config_file=/Caddyfile config_adapter=

Alles anzeigen

chente · 12. Dezember 2023

There is some conflict with port 53. OMV needs that port. Do you have any other containers that use this port too?

jc-59 · 12. Dezember 2023

I've stopped all other containers.

Portainer is the only one running

jc-59 · 12. Dezember 2023

port 53 is the DNS port

sonnyhill · 16. Dezember 2023

Hello:

I have nexcloud aio running with automatic updates.

I have been receiving the following error after overnight backups that disable nextcloud:

Code

Fatal error: Uncaught Exception: Could not pull image nextcloud%2Faio-redis%3Alatest. Please run 'sudo docker exec -it nextcloud-aio-mastercontainer docker pull nextcloud%2Faio-redis%3Alatest' in order to find out why it failed. in /var/www/docker-aio/php/src/Docker/DockerActionManager.php:589

As instructed, I ran:

Code

sudo docker exec -it nextcloud-aio-mastercontainer docker pull nextcloud%2Faio-redis%3Alatest

with the resulting response:

invalid reference format: repository name must be lowercase

I have attempted to access /DockerActionManager.php:589, but to do so requires a password for www-data, which I do not have and did not set even though I am the administrator and only person who uses the system.

I used the guide to set up nextcloud-aio, so I did not manually set the case of the name of the repositories.

Anyone have an idea of what steps I need to take to clear this error? Thanks.

claydoh · 16. Dezember 2023

Zitat von sonnyhill
As instructed, I ran:
Code
sudo docker exec -it nextcloud-aio-mastercontainer docker pull nextcloud%2Faio-redis%3Alatest
with the resulting response:

invalid reference format: repository name must be lowercase

The command presented has escape code characters instead of slashes and equal signs. Replace "%2F" with a "/" and "%3A" with ":"

Hopefully any error will show why it could not pull the image.

sonnyhill · 16. Dezember 2023

I made the replacements, but am still receiving an error::

Code

$ sudo docker exec -it nextcloud-aio-mastercontainer docker pull nextcloud/aio-redis=latest
invalid reference format

claydoh · 16. Dezember 2023

Oops, I did a typo. It should be a ":" instead of an "=" here, just like in a compose file.

Edited for reference.

sonnyhill · 17. Dezember 2023

Thanks claydoh!

I made the correction and received the following response:

Code

$ sudo docker exec -it nextcloud-aio-mastercontainer docker pull nextcloud/aio-redis:latest
latest: Pulling from nextcloud/aio-redis
Digest: sha256:58c76d34d7a4d05133cdb0883ffec0276f690dcccd6512cadc37d70c4e176342
Status: Image is up to date for nextcloud/aio-redis:latest
docker.io/nextcloud/aio-redis:latest

is there anyway I can access a log file to determine what is causing the exception?

claydoh · 17. Dezember 2023

The output seems to indicate that it has pulled the image successfully, so maybe you need to restart the container(s), probably from the AIO admin panel if that is accessible. Perhaps restarting the AIO main container from OMV will do this on its own?

sonnyhill · 17. Dezember 2023

I already stopped the containers and started them to get nextcloud up and running again. That probably cleared the exception. I have been getting this error every three or so days. Next time that it happens I will use the corrected code that you provided above before stopping the containers and restarting to see if the exception is identified.

Thanks for all of your help!

NEXTCLOUD AIO WITH PROXY : PB during first access at https://[SERVER_IP]:8080

Proxy Error

Jetzt mitmachen!

Tags