Hey @Alejandro_Sophila, you can make this work with the single VPS. Personally, I would just replace Caddy with boringproxy unless you need/want special features provided by Caddy (it has many useful features that boringproxy is lacking). In this case, for the services running directly on the VPS, in boringproxy when adding the tunnels you would use the following settings:
- Tunnel Port set to whatever port the service is running on
- Client Name set to No Client
- TLS Termination set to Server HTTPS
If you decide to leave Caddy in place, you’ll need to run boringproxy behind it. Note that others have run into issues with running other reverse proxies behind boringproxy. I feel like there are still some bugs with this setup. See here. I think you’ll need to use several options when running the server, including -allow-http, -behind-proxy, -http-port, -https-port.