Android SSL (HTTPS) can't login to Subsonic Server

[ninjapuffin]

Hello,

I am trying to setup the Subsonic Server to use HTTPS (SSL) and work with the Android App.
I went in to the server control panel and set activated the HTTPS feature, restarted server no problems.
Logged in via the web page, notice it was using https which was great so I thought everything was fine.
I then tried to login via the Android App and got the error connection error. I then tried to change the music server to: https://<name>.subsonic.org
https://<name>.subsonic.org:4443
http://<name>.subsonic.org
none of these worked all gave the connection error message.
Does the Android App work with https?
What have I not setup correctly?

Thanks

[mr_nobody]

Yes https works with the android app. The address you have that includes both the "https" part as well as the port number is what I use. That being said, I do not use a subsonic.org address...not sure if that is an issue or not.

[bushman4]

If you are using a subsonic address then you should NOT use https in the front of the address... it should just be http://yourdomain.subsonic.org.

Earlier versions of the app didn't seem to like any capitalization, so I always use lowercase. Not sure if that is still an issue.

That being said, your problem is most likely that you need to open the ssl port on your router and map it to the ip address of the subsonic server like you did with the regular non-ssl port.

Glenn

[ninjapuffin]

Thanks Glenn you were right I had forgotten to map the new 4443 port in my router and now the Android app connects.
This brings up another question which is how do I know if the Android app is using the SSL connection vs. the non-SSL connection.
The fact is that I have both the 4040 and 4443 ports open, so is there any indication in the app which it is using?

thanks

[bushman4]

If you have SSL enabled then the only thing that Subsonic ever replies on the HTTP port is "302 - Temporarily moved, try https://your.ip.address:YourPort/YourContextPath. "

So if SSL is turned on it has to be using SSL or it would not be working.

Glenn