I am looking to make my home server safely host LT so it is available to all my devices wherever I am. I’ve successfully got the docker version running on Debian so that I can curl the LAN address (192.168.0.202:8081/v2) and get a response from LT from any device on the network. I can set up port forwarding on my router and get access to the server anywhere, but only unencrypted http which is too dangerous.
I already have Nginx running on 192.168.0.202 to serve my Nextcloud instance and a friend’s Nextcloud instance. But I am pretty new to using Docker and a novice at Nginx, and I am not sure the right way to put it behind a reverse proxy for the HTTPS upgrade.
I see some people online mentioning changing the parameters in the docker compose file, and others talking about writing new server block configurations in the sites-available section of nginx configuration. I use a ddns domain and Let’s Encrypt via certbot for that domain, so it is like example.ddns.net. I would like to be able to have something like lt.example.ddns.net, example.ddns.net/lt, or even example.ddns.net:8081 and have it access my 192.168.0.202 server behind encryption.
I don’t understand why I would need to change any docker compose parameters if I can successfully access the server. It seems like I would just need to put it behind a reverse proxy and that takes requests to lt.example.ddns.net on port 80 and forwards them to 192.168.0.202 on port 8081 with HTTPS upgrade. Can someone tell me if I am on the right track?
Thanks!