Moving between a reverse proxy aio instance and a vanilla one

[MichaelFliegner]

Can I restore a reverse proxy aio instance to a vanilla one using backup?

My source instance was created using the compose.yaml from the aio repo with just the lines for using caddy uncommented.

I tried to restore a remote backup into a new vanilla instance, but got connection refused on opening the instance. The apache container is listening on 11000, but nobody is there to do the forwarding.
Can I make the mastercontainer do that again? Or is restoring only possible with the original reverse proxy compose.yaml?

This is relevant for me as I want to be able to restrict the home network instance to local only access, but also be able to restore it on a vps without reverse proxy and pi-hole.

[szaimen]

Have you set APACHE_PORT to 443 and APACHE_IP_BINDING to 0.0.0.0?

[MichaelFliegner]

like this?

remove the masterconter after restore of the reverse proxy instance from backup

sudo docker run --init --sig-proxy=false --name nextcloud-aio-mastercontainer --restart always --publish 80:80 --publish 8080:8080 --publish 8443:8443 --env APACHE_PORT=443 --env APACHE_IP_BINDING=0.0.0.0 --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock:ro ghcr.io/nextcloud-releases/all-in-one:latest

no success:

This site can’t provide a secure connection

agdaz.online sent an invalid response.

ERR_SSL_PROTOCOL_ERROR

[szaimen]

You need to first visit the AIO interface and restart the containers. Only then are changes applied to the sibling containers.

[MichaelFliegner]

It’s the LetsEncrypt too many certificates error. I don’t understand when exactly certificates are consumed. One obtainable is obviously not enough.

[MichaelFliegner]

Jetzt habe ich es geschnallt. Gerade habe ich meine Cloud steilo.michaelfliegner.de von vanilla auf reverse proxy umgestellt und eine wordpress instanz daneben installiert wp.michaelfliegner.de
Danke!