# Cannot access Nextcloud after enabling Caddy community container **URL:** \ **Category:** ℹ️ Support\ **Tags:** caddy, wopi, aio\ **Created:** [May 9, 2026, 10:27am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280 "2026-05-09T10:27:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![fooforever](https://help.nextcloud.com/user_avatar/help.nextcloud.com/fooforever/32/78322_2.png) [@fooforever](https://help.nextcloud.com/u/fooforever)\ **Post date:** [May 9, 2026, 10:27am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/1 "2026-05-09T10:27:30Z")
> **Support intro** > > ## Sorry to hear you’re facing problems. 🙁 > > _The community help forum ([help.nextcloud.com](http://help.nextcloud.com)) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are **volunteering their time to help you.** _ > > **If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via [portal.nextcloud.com](http://portal.nextcloud.com) where Nextcloud engineers can help ensure your business keeps running smoothly.** > > ## Getting help > > In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can. > > **Before clicking submit** : Please check if your query is already addressed via the following resources: > > - [Official documentation](https://docs.nextcloud.com) (searchable and regularly updated) > - [How to topics and FAQs](https://help.nextcloud.com/c/how-to-faqs/9) > - [Forum search](https://help.nextcloud.com/search) > > (Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly). Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. ❤ ## The Basics - Nextcloud Server version _(e.g., 29.x.x)_: - `Nextcloud AIO 12.9.2 - Nextcloud Hub 25` - Operating system and version _(e.g., Ubuntu 24.04)_: - `Ubuntu 24.04` - Web server and version _(e.g, Apache 2.4.25)_: - `Built in with AIO` - Reverse proxy and version \_(e.g. nginx 1.27.2) - `Built in with AIO` - PHP version _(e.g, 8.3)_: - `Built in with AIO` - Is this the first time you’ve seen this error? (Yes / No): - `Yes` - When did this problem seem to first start? - `After enabling Caddy community container from AIO interface` - Installation method _(e.g. AlO, NCP, Bare Metal/Archive, etc.)_ - `AIO via Linode marketplace app` - Are you using CloudfIare, mod\_security, or similar? _(Yes / No)_ - `No` ### Summary of the issue you are facing: I enabled the Caddy community container in NC AIO with the hope of being able to host extra services on the same server as my Nexcloud install. The docs said it was self configuring for Nextcloud and the auto supported services via the env variables. However after restarting all the containers I was left not being able to connect to Nextcloud, which was working fine before. I guessed that the Caddy container didn’t auto config in the way I thought it was going to, so I disabled it. But this hasn’t resolved my problem, I’m still unable to connect to NC and get a `SSL_ERROR_INTERNAL_ERROR_ALERT` in the browser when I try. I still have a AIO admin tab open which works, but new connections don’t. So I think the certificates have been messed up by enabling the not properly configured Caddy container. I have started everything including the server and no change. How can I get access back? ### Log entries docker logs nextcloud-aio-apache: ```auto Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Waiting for Nextcloud to start... Connection to nextcloud-aio-nextcloud (172.18.0.2) 9000 port [tcp/*] succeeded! [Fri May 08 22:47:15.044255 2026] [mpm_event:notice] [pid 56:tid 56] AH00489: Apache/2.4.66 (Unix) configured -- resuming normal operations [Fri May 08 22:47:15.044370 2026] [core:notice] [pid 56:tid 56] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' ``` docker logs nextcloud-aio-nextcloud: ```auto Waiting for database to start... Connection to nextcloud-aio-database (172.18.0.6) 5432 port [tcp/postgresql] succeeded! now ------------------------------- 2026-05-08 22:46:33.149579+01 (1 row) + '[' -f /dev-dri-group-was-added ']' ++ find /dev -maxdepth 1 -mindepth 1 -name dri + '[' -n '' ']' + set +x Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded! Applying one-click-instance settings... System config value one-click-instance set to boolean true System config value one-click-instance.user-limit set to integer 100 System config value one-click-instance.link set to string https://nextcloud.com/all-in-one/ support already enabled Adjusting log files... System config value upgrade.cli-upgrade-link set to string https://github.com/nextcloud/all-in-one/discussions/2726 System config value logfile set to string /var/www/html/data/nextcloud.log Config value were not updated System config value updatedirectory set to string /nc-updater System config value maintenance_window_start set to integer 100 Applying network settings... System config value allow_local_remote_servers set to boolean true System config value davstorage.request_timeout set to integer 3600 System config value trusted_domains => 1 set to string nextcloud.xxx.co.uk System config value overwrite.cli.url set to string https://nextcloud.xxx.co.uk/ System config value documentation_url.server_logs set to string https://github.com/nextcloud/all-in-one/discussions/5425 System config value htaccess.RewriteBase set to string / .htaccess has been updated System config value dbpersistent set to boolean false System config value auth.bruteforce.protection.enabled set to boolean true System config value ratelimit.protection.enabled set to boolean true System config value files_external_allow_create_new_local set to boolean true notify_push is up-to-date or no updates could be found System config value trusted_proxies => 0 set to string 127.0.0.1 System config value trusted_proxies => 1 set to string ::1 System config value trusted_proxies => 10 set to string 172.18.0.0/16 Config value were not updated + echo nextcloud-aio-collabora + grep -q 'nextcloud-.*-collabora' + COLLABORA_HOST=nextcloud.xxx.co.uk + set +x richdocuments is up-to-date or no updates could be found Config value 'wopi_url' for app 'richdocuments' is now set to 'https://nextcloud.xxx.co.uk/', stored as mixed in fast cache No IPv6 address found for nextcloud.xxx.co.uk. Config value were not updated System config value enabledPreviewProviders => 0 set to string OC\Preview\Imaginary System config value enabledPreviewProviders => 23 set to string OC\Preview\ImaginaryPDF System config value preview_imaginary_url set to string http://nextcloud-aio-imaginary:9000 System config value preview_imaginary_key set to string cd341dc17d6a7f48311910f2310e07721b30fac7fa2a7d03 + '[' true = true ']' + '[' 11000 = 443 ']' + set +x Waiting for nextcloud-aio-apache to become available... [08-May-2026 22:47:11] NOTICE: fpm is running, pid 206 [08-May-2026 22:47:11] NOTICE: ready to handle connections Connection to nextcloud-aio-apache (172.18.0.7) 11000 port [tcp/*] succeeded! Activating Collabora config... ✓ Set WOPI url to http://nextcloud-aio-apache.nextcloud-aio:23973 ✓ Set callback url to http://nextcloud-aio-apache.nextcloud-aio:23973 Checking configuration 🛈 Configured WOPI URL: http://nextcloud-aio-apache.nextcloud-aio:23973 🛈 Configured public WOPI URL: https://nextcloud.xxx.co.uk 🛈 Configured callback URL: http://nextcloud-aio-apache.nextcloud-aio:23973 ✓ Fetched /hosting/discovery endpoint ✓ Valid mimetype response ✓ Valid capabilities entry ✓ Fetched /hosting/capabilities endpoint ✓ Detected WOPI server: Collabora Online Development Edition 25.04.9.4 Collabora URL (used for Nextcloud to contact the Collabora server): http://nextcloud-aio-apache.nextcloud-aio:23973 Collabora public URL (used in the browser to open Collabora): https://nextcloud.customnothing.co.uk Callback URL (used by Collabora to connect back to Nextcloud): http://nextcloud-aio-apache.nextcloud-aio:23973 ``` ---
**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\ **Post date:** [May 10, 2026, 1:02pm UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/2 "2026-05-10T13:02:21Z")
Hi, you probably want to check the caddy container logs in order to debug this… ---
**Author:** ![fooforever](https://help.nextcloud.com/user_avatar/help.nextcloud.com/fooforever/32/78322_2.png) [@fooforever](https://help.nextcloud.com/u/fooforever)\ **Post date:** [May 10, 2026, 1:09pm UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/3 "2026-05-10T13:09:04Z")
I don’t have a caddy container running ```auto docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 673f9b61450f ghcr.io/nextcloud-releases/aio-apache:latest "/start.sh /usr/bin/…" 21 minutes ago Up 21 minutes (healthy) 80/tcp, 11000/tcp nextcloud-aio-apache 19c344c031fe ghcr.io/nextcloud-releases/aio-nextcloud:latest "/start.sh /usr/bin/…" 21 minutes ago Up 21 minutes (healthy) 9000/tcp nextcloud-aio-nextcloud 5a0a3758ce7c ghcr.io/nextcloud-releases/aio-imaginary:latest "/start.sh" 21 minutes ago Up 21 minutes (healthy) nextcloud-aio-imaginary e99fd3d67545 ghcr.io/nextcloud-releases/aio-redis:latest "/start.sh" 21 minutes ago Up 21 minutes (healthy) 6379/tcp nextcloud-aio-redis 6b307d8b5d48 ghcr.io/nextcloud-releases/aio-postgresql:latest "/start.sh" 21 minutes ago Up 21 minutes (healthy) 5432/tcp nextcloud-aio-database 7cc729ce6d22 ghcr.io/nextcloud-releases/aio-notify-push:latest "/start.sh" 21 minutes ago Up 21 minutes (healthy) nextcloud-aio-notify-push dbb5276dd101 ghcr.io/nextcloud-releases/aio-collabora:latest "/start-collabora-on…" 21 minutes ago Up 21 minutes (healthy) 9980/tcp nextcloud-aio-collabora b08761cef7d4 ghcr.io/nextcloud-releases/aio-borgbackup:latest "/start.sh" 2 hours ago Exited (0) About an hour ago nextcloud-aio-borgbackup 895eaa50c512 ghcr.io/szaimen/aio-caddy:v4 "/start.sh" 42 hours ago Exited (143) 42 hours ago nextcloud-aio-caddy 2519b6b5e957 ghcr.io/nextcloud-releases/aio-watchtower:latest "/start.sh" 6 days ago Exited (0) 6 days ago nextcloud-aio-watchtower d6871985c8d6 nextcloud/all-in-one:latest "/start.sh" 3 weeks ago Up 39 hours (healthy) 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, [::]:8443->8443/tcp, 9000/tcp nextcloud-aio-mastercontainer 7a88af9c586d ghcr.io/nextcloud-releases/aio-whiteboard:latest "/start.sh" 7 months ago Exited (1) 7 months ago nextcloud-aio-whiteboard 4ed40b7747be ghcr.io/nextcloud-releases/aio-talk:latest "/start.sh superviso…" 7 months ago Exited (0) 7 months ago nextcloud-aio-talk ``` doing a `docker logs nextcloud-aoi-caddy` doesn’t print anything ---
**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\ **Post date:** [May 11, 2026, 7:24am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/4 "2026-05-11T07:24:22Z")
> [@fooforever](#): > > docker logs nextcloud-aoi-caddy Have you tried `sudo docker logs nextcloud-aio-caddy` ? ---
**Author:** ![fooforever](https://help.nextcloud.com/user_avatar/help.nextcloud.com/fooforever/32/78322_2.png) [@fooforever](https://help.nextcloud.com/u/fooforever)\ **Post date:** [May 11, 2026, 7:39am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/5 "2026-05-11T07:39:07Z")
Yes, still no output. What config does the adding the caddy community container change within the main AIO containers? There must be something that changed when enabling/disabling that now isn’t set up as it was before. Thanks for your help. ---
**Author:** ![fooforever](https://help.nextcloud.com/user_avatar/help.nextcloud.com/fooforever/32/78322_2.png) [@fooforever](https://help.nextcloud.com/u/fooforever)\ **Post date:** [May 11, 2026, 7:54am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/6 "2026-05-11T07:54:10Z")
I have missed the removing the reverse proxy section in the readme: [all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#8-removing-the-reverse-proxy) Following the steps here has got me back up and running. Seen as I never manually stopped the master container this wasn’t obvious to me that it would have changed the port bindings. ---
**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\ **Post date:** [May 19, 2026, 7:54am UTC](https://help.nextcloud.com/t/cannot-access-nextcloud-after-enabling-caddy-community-container/244280/7 "2026-05-19T07:54:52Z")
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.