Page 1 of 1

Connecting via Android client SSL issues

PostPosted: Tue Jan 31, 2012 1:26 am
by linuxman
Ok if I change the SSL port to anything other than 443 the android client will not connect unless there is no SSL port defined and the default disabled is in effect.

Apparently the client connects on the default port and switches over to SSL during the test connection and any port other than 443 fails.

Why is this and how can it be changed so that the client would run on same port as the server is running? I tried the default 4040 and putting SSL at 4041 and it would not connect until I switched back to 443.

Re: Connecting via Android client SSL issues

PostPosted: Wed Feb 01, 2012 4:03 am
by GJ51
I'm no expert with Linux, but I always use 44X for SSL - except for 443 because it is to commonly used by other applications. I'd try 445 and then test with canyouseeme.org to make sure that the port is being forwarded correctly and that the firewall is not blocking the port.

Re: Connecting via Android client SSL issues

PostPosted: Wed Feb 01, 2012 5:30 am
by linuxman
Well the browser works fine for any ports but the android subsonic client fails when any other port is used besides 443. I want to know if there is a xml file or anything on the phone that can be edited so that it won't try and connect ssl on just 443.

Re: Connecting via Android client SSL issues

PostPosted: Wed Feb 01, 2012 6:40 am
by GJ51
I have no problem reaching any of my servers on any ports. EVO 4G.

Test your phone on my server.


I'll PM you the link.