SNAP Installation change php, apache and nextcloud configs

[mactrent]

@Bernd_Wechner

Puzzling to me is that whenever I restart the snap that file is respected but totally reformatted and comments removed. Some weird stuff happening under the hood that I wish I understood.

My guess is that the snap includes a validator, which parses the config settings and writes the file again to apply any changes it might (or might not) make.

@Bernd_Wechner

I am curious in your example is reverse_proxy_ip the LAN IP or the WAN IP of the reverse proxy? I have set it to the LAN IP, the WAN IP is trickier as it’s variable and I use DDNS.

Mine is also set to the reverse proxy’s LAN IP, which would be 192.168.0.1 in your case.

@Bernd_Wechner

I [used nc on port 80] to watch incoming request while I reloaded the WAN URL and surprisingly got something. Srprising because I load https://mynexcloud.mydomain.tld, an https URL in Google Chrome. I expect that to arrive on port 443 only.

Your reverse proxy is listening on port 443, so that’s where the initial HTTPS connection requests (Request A) go. The proxy forwards each request to the Nextcloud snap via the URL we gave in the ProxyPass directive: http://192.168.0.14/ (Request B).

My container’s Apache expects connections on port 80, and answers directly.
The snap’s Apache configaration might just respond to all requests on port 80 (HTTP) with a redirect to port 443 (HTTPS). The client obediently opens a new request to port 443, which the reverse proxy forwards again to port 80, and we’ve got a loop.

Instead, you’ll need to change the ProxyPass URL to Nextcloud’s HTTPS port (443 by default): https://192.168.0.14/. The snap doesn’t have a valid SSL certificate, but that’s why we have the SSLProxyCheck options off in the reverse proxy’s config.

Edit: I misread the nc log, and thought Nextcloud was on the same box. Also, diagrams.net is the best.