i have libresonic setup in docker. i can access with internal ip but cant access with external ip. are there any how to's for this setup? i have nextcloud and letsencrypt setup and running.
Access Libresonic externally
-
- OMV 4.x
- jo3Lp
-
-
I've wondered this myself but haven't had the opportunity to really look into trying to set it up. You could (in theory) just forward your Libresonic port in your router to your NAS, but it would be unsecured just using port forwarding.
-
If you have letsencrypt running you can access through a subdomain and the reverse proxy
-
Hi Morlan, Can you give me a quick tutorial on how to do the reverse proxy. sorry i'm a noob
-
How did you set up letsencrypt? Docker compose?
-
I followed the TDL video for nextcloud, letsencrypt and duckdns
-
Setup Libresonic and join it in the docker network of letsencrypt (via network tab of docker gui).
Then open ssh session and go to cd appdata/letsencrypt/nginx/proxy-confs/ then nano libresonic.subdomain.conf enter this:Code
Alles anzeigenserver { listen 443 ssl; listen [::]:443 ssl; server_name libresonic.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_libresonic libresonic; proxy_pass http://$upstream_libresonic:4040; } }
then you have to add the subdomain "libresonic" to your letsencrypt container and restart it. Also for this to work your libresonic container needs to be named libresonic.
-
Morlan, Thank you for the instructions, I'll give it a shot soon and report back, all this linux stuff is new to me
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!