The Basics
- Nextcloud Server version (e.g., 29.x.x):
31.0.10
- Operating system and version (e.g., Ubuntu 24.04):
Debian 13
- Web server and version (e.g, Apache 2.4.25):
Apache AIO
- Reverse proxy and version _(e.g. nginx 1.27.2)
Caddy
- PHP version (e.g, 8.3):
AIO
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
few minutes after installation
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Nextcloud containers seem to have an dns resolv issue.
Talk signaling and Collabora office wont work with a resolution of the Nextcloud domain.
Rest of the nextcloud is working.
The test mentioned in the github reverse proxy thread give me no solution.
nc -z localhost 11000; echo $? gives me 1, but I cannot found out what is the actual problem.
Caddy as reverse proxy is set like in github example domain on port 443 and then to ip from local host with 11000 as apache port
my start command:
``sudo docker run --init --sig-proxy=false --name nextcloud-aio-mastercontainer --restart always --publish 8080:8080 --env APACHE_PORT=11000 --env APACHE_IP_BINDING=192.168.2.252 --env APACHE_ADDITIO
NAL_NETWORK="" --env SKIP_DOMAIN_VALIDATION=false --env NEXTCLOUD_DATADIR="/mnt/temp/_data" --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock
:ro nextcloud/all-in-one:latest``
Edit: I know changed the host in /etc/hosts to point on the and it works right now.
sudo nano /etc/hosts
127.0.0.1 localhost
192.168.2.252 nextcloud