Can't access my AIO instance after ip address changed

[2flkw9fv]

The Basics

• Nextcloud Server version (e.g., 29.x.x):
  • Nextcloud 30.0.2
• Operating system and version Ubuntu 24.04
• Reverse proxy: Caddy v2.8.4
• When did this problem seem to first start? When the ip address changed from what I used to set up AIO.
• Installation method
  - Nextcloud AIO v10.0.0
• Are you using CloudfIare, mod_security, or similar? Yes: Cloudflare, just as the nameserver. Same when caching is bypassed

Summary of the issue you are facing:

My domain gives an Error 523, but I can access the AIO interface itself.
After some troubleshooting with my ISPI changed routers.
I changed to the new ip address here:

• Configuration.json with sudo docker run -it --rm --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config:rw alpine sh -c "apk add --no-cache nano && nano /mnt/docker-aio-config/data/configuration.json" ,
• trusted domains in config.php
• in my router’s port forwaring settings
• The A record in Cloudflare to point to the new public ip
• in theCaddyfile:

 example.com:443{
reverse_proxy 192.168.0.18:11000
}

What else do I need to change or set up?

Log entries

Nextcloud

https://paste.grin.hu/KGrxioyu

[wwe]

are you really try setup your system using “example.com”? as long you don’t own this domain this will not work.

2024-12-13T20:56:39.281901076Z System config value trusted_domains => 1 set to string example.com
2024-12-13T20:56:40.019561720Z System config value overwrite.cli.url set to string https://example.com/
...
2024-12-13T20:57:25.475092242Z Failed to fetch discovery endpoint from https://example.com
2024-12-13T20:57:25.475127603Z Server error: `GET https://example.com/hosting/discovery` resulted in a `523 ` response:
2024-12-13T20:57:25.475133779Z error code: 523

[2flkw9fv]

No, the template just said I should replace my data when sharing it

[wwe]

using “example.com” is not the best choice. but the problem remains the same - your server can not access your domain which results in the same troubleshooting sequence:

• start on the client and review the DNS and IP your domain resolves to
• access the URL and review if you see the connection in the very first system on this IP (firewall or reverse proxy)
• if you see the request, check the destination and if there are any errors
• continue until you get to the final system and analyze if the request arrives and process as expected

[2flkw9fv]

just in case someone encounters it:
It turns out the Vodafone router reset its port forwarding settings after the ISP changed some settings.

I also changed my /etc/caddy/Caddyfile to

domainname.com:443 {
    redir /.well-known/carddav /remote.php/dav 301
    redir /.well-known/caldav /remote.php/dav 301

    reverse_proxy localhost:11000
}

instead of using the local ip address.

then restarted everything and now it works. thanks for the tips