Installing Cloudron behind a reverse proxy

[ianhyzy]

@nebulon Basically I'm trying to run cloudron at home and I have a Synology NAS running docker containers with a lot of stuff. Previously, I was running Cloudron in a VPS so I setup a raspberry pi at home to run caddy and act as a reverse proxy for the Synology services (Sonarr, Radarr, etc). Now I'm trying to figure out how to get them to coexist where Cloudron can operate normally but I can keep the docker containers on the NAS and proxied to a subdomain. For example, sonarr.ian.gay is proxied to a Sonarr container on the NAS, but I want to make sure blog.ian.gay still proxies to the Wordpress installation on Cloudron.

[girish]

@ianhyzy In theory, it should work with https proxying. See also this thread - https://forum.cloudron.io/topic/4463/cloudron-and-apps-behind-a-proxy/ . Do you see any errors in the caddy logs?

You can test quickly if it is some networking issue or configuration error. From the server where caddy is installed:

curl -k -H 'Host: ian.gay' https://191.168.1.203

If the above works, it is some configuration issue.

[ianhyzy]

@girish Oddly, it did fail:

pi@raspberrypi:/etc/caddy $ curl -k -H 'Host: ian.gay' https://191.168.1.203
curl: (7) Failed to connect to 191.168.1.203 port 443: Connection timed out

Going to did around in that other thread a bit, if it's easier to just use NGINX on cloudron I'll swap the rules over

[girish]

@ianhyzy could it be that the IP address of cloudron is incorrect?

[ianhyzy]

@girish Nope, I did double check and the IP is 192.168.1.202 but it fails with the same timout. If I remove the Caddy proxy and just forward 80/443 to Cloudron to get it setup, can I just migrate the rules over to /etc/nginx/nginx.conf? I feel like that would be easier over the long run

[girish]

@ianhyzy the nginx config is managed by Cloudron and there is a risk it will get overwritten across updates. This doesn't happen often, so maybe you can just add new configs under /etc/nginx/applications but be sure to keep a copy of those extra configs, so you can put them back in case Cloudron over wrote it. Note that Cloudron will only overwrite a Cloudron update that updates the internal nginx configuration templates (so it doesn't happen all that often but happens every 2-3 releases or so).

[ianhyzy]

@girish I'm setting this up now, just to start I created a file called proxy.conf:

http {
server {
    listen 80;
    server_name sonarr.ian.gay;

    location /sonarr {
       proxy_pass http://192.168.1.201:8989;
    }
}
}

This seems to work just fine (and I will be backing the configs up like you said). Can I safely use Certbot with these to enable HTTPS (understanding I may need to set it up again if it gets wiped). From what I see online it's just certbot --nginx and then specifying the domain.

[ianhyzy]

@ianhyzy I just backed up my configs and tried it anyway, it worked - I just needed to remove http {} from the file.

[robi]

it's useful to create separate configs for all apps you have custom settings for.. in this case sonarr.conf among the others.

[ianhyzy]

@robi is there a safe/easy way to point Syncthing or a similar tool at these directories or should this be a manual task?

[robi]

@ianhyzy for nginx configs? No, they're on the Cloudron host.