Portless HTTPS setup using the new ssl features #1379
carsoni
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've been trying for a while to setup a port-less https connection to snapweb e.g. calling https://musicserver.example.com and getting to the snapweb with fully working features.
I finally got this working this morning and thought I would share the setup. I know it's not directly related to snapcast but it seemed like this might be useful info for users.
The basic architecture is to have a running snapserver - let's say on musicserver.example.com but just on http so access to snapweb would be via port 1780 - http://musicserver.example.com:1780
Then put an nginx proxy in front to catch and proxy calls to https://musicserver.example.com into 127.0.0.1:443. NB To maintain other https access to the server it's best to have the nginx server settings listen on the IP address of the server to avoid :443 clashes
And make the necessary adjustments to snapserver.conf to have it listen on 127.0.0.1:443 (actually the nginx file proxys to https://127.0.0.1) for the proxied calls.
Assuming your snapserver is up and running on http here are the snapserver.conf changes and the nginx site setting. Note that the certificate san and the "host" entry in snapserver.conf need to match.
Now you have clean secure access to snapweb with no ugly port numbers in the URL and images showing up in the UI. :-)
SNAPSERVER.CONF
NGINX SITE FILE
Beta Was this translation helpful? Give feedback.
All reactions