AIO with reverse proxy from community containers

Stupid question, when using the community containers for a reverse proxy, e.g. the caddy one, do I still need to follow the reverse-proxy.md first and change the docker config of the mastercontainer be including for example

--env APACHE_PORT=11000 \

or do I use the standard AIO config and just install die community container?

I have my AIO instance currently running with a separate NPM docker container and want to switch to a community container. Hence I wonder if I have to change my master container’s config back to “standard” before installing the community container or just leave it as it is and install the community container.

So you want to use the caddy community container? In that case I think you should remove npm and then add caddy and it should work (you dont need to adjust anything). Let me knoe if you run into problems :slight_smile:

1 Like

Yep, worked without issues.

1 Like

@szaimen I am afraid, that there is an issue, Since I use caddy the daily backup fails. See AIO: Daily backup does not start/finish

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.