4 Using https For improved security you can turn on https encryption. On Windows, open the Subsonic Control Panel by clicking on the Subsonic tray icon, then enable https on the specified port (default 443).
On Linux, add --https-port=4443 (or any other port) to SUBSONIC_ARGS in /etc/default/subsonic (Ubuntu/Debian) or /etc/sysconfig/subsonic (Fedora/RPM).
Can anyone please give instructions on how to do this on the ReadyNas?
I couldn't find /etc/default/subsonic (running subsonic add-on 2.0 with ffpmeg add-on 1.2)
run /etc/frontview/addons/bin/SUBSONIC/stop.sh /etc/frontview/addons/bin/SUBSONIC/start.sh
If you now try to access Subsonic with http on the standard port 4040 it will automatically redirect you to https on port 4043 (or whatever you choose).
Im trying to enable HTTPS aswell. I don't have root-access to my Ultra 2, do I need to have it? I can edit subsonic.sh as described in the thread, but since I lack root I'm not able to run stop.sh and start.sh. I tried editing the subsonic.sh and then just restarting Subsonic in the Frontview UI. But after stoping the service I couldn't start it again. Not even after editing the file back to normal. Must be a permissions thing I guess. So, any tips on achieving this without root access?
After I change the destination address for the subsonic interface, how to I get the button in Frontview to point to the new location? I can get to it manually, just curious how to modify the button so it works too. Thanks guys.
Subsonic has been working 100% for me the last few months with HTTPS enabled but all of a sudden it refused to decode FLAC-->Mp3. I tried everything but I eventually gave up and did a clean install on my Readynas ultra 4.
Now I can't get HTTPS working again. I've tried editing the subsonic.sh but this time it simply doesn't work. I have these lines: SUBSONIC_PORT=4040 SUBSONIC_HTTPS_PORT=4043
I've tried setting the SUBSONIC_PORT=0 but then everything failes. What am I doing wrong here?
@honoka : Other than 'gain root access' ?... no @xsspeed03 : hack thr frontview sources, but then you might mess up things.... why changing url anyway ? @xophile : hmm... mine is running on a NVX, perhaps the Ultra 4 is lacking some SSL/TLS libraries ?
I forgot I put that post here. I actually figured out how to change where the button in Frontview directs to. The reason for this is because the firewall at my workplace will not allow me to get to port 4040, but a higher port works fine. So I just changed the port that Subsonic uses.
If you are running this from work, you might really consider running subsonic using https to avoid traffic monitoring...
[paranoid mode=on] With http your subsonic credentials will be transported in the clear.... not the most optimal arrangement to run over the internet. [/paranoid]
That's a very good point. I tried going though the steps above to enable https, but can't get it to work. I get an error page. Something about the SSL record being too long. Any ideas?
Great news, friends ! I found how to make it work using the latest release...
you have to edit subsonic.sh, adding the SUBSONIC_HTTPS_PORT=4043 thing, as we had to do...
BUT... the way arguments are passed seems to have changed, and the bottom of the script lacks a line for sending the https port. so, you must add -Dsubsonic.httpsPort=${SUBSONIC_HTTPS_PORT} \ near the other arguments lines... And then, it looks like:
looks like SuperPoussin made the update for passing arguments I was talking about previously, in the latest plugin version. All you have to do now is as before, setting the SUBSONIC_HTTPS_PORT variable.
