Caddy community version - how to safely remove?

[codewordcreative]

Basic info

• Nextcloud Server version: 32, AIO Nextcloud Docker setup
• Operating system and version: Ubuntu 24.04
• Repeatable error
• Started on installing Nextcloud Caddy
• Not using Cloudflare DNS

Summary of the issue you are facing:

I installed Docker AIO with everything working (including talk, uploads, sync). Then I installed the Caddy community version. As expected, I restarted the containers to regain access, but now I am unable to remove it.

Steps to replicate it

1. Install Caddy.
2. Try deactivating or removing it…
3. Then it is impossible to access the main Nextcloud area - only the AIO admin area remains accessible.
4. Access is possible again only on restoring the container.
5. …If only it were possible to know what to do to reverse the changes?

It’s pretty much exactly what this person on Reddit describes. I feel like some sort of deactivation and restoration mechanism/instructions would help…

https://www.reddit.com/r/NextCloud/comments/1n1td4d/broke_my_nextcloud_aio_setup_after_caddy_container/

[szaimen]

Hi, can you restore a backup from before adding the caddy community container? This should make it work again.

[codewordcreative]

I hadn’t made one… I was really hoping there would be a simpler way than just ‘restore from backup’ - if it was made clear what changes are made, it may be possible to undo them. It isn’t right that there is no option to safely uninstall a container - without any warning in the AIO interface that it may make permanent changes to the system that cannot be undone. There is a warning, but there’s an assumption things can be undone. This is particularly important given the fact it changes ports and can mess up apps.

[szaimen]

It changes these settings internally: all-in-one/community-containers/caddy/caddy.json at 4acd1537bf50e72af8f906f74e04180c0c6b786a · nextcloud/all-in-one · GitHub

You can undo this like so: all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub