Subsonic problem over HTTPS

[Eshezo]

Hi All,

Subsonic version: 4.9(build 3853) Premium
Server: Jetty-6.1.x, java 1.7.0_51, Windows 7

http on port 4040 which works fine, both local LAN and external

when I switch on the https option which is port 443 I can only access it from the local server / LAN , all external access stops working.

I've checked the port forwarding and both 4040 and 443 are forwarded correctly, although when checking with a port checker it only ever shows 4040 as open.

If I stop the subsonic service 4040 also shows closed on a port checker.

Everything was working fine until I received a message that I needed to upgrade to premium to continue streaming to my mobile devices, thats fine I paid for premium received the key and registered it, subsonic reflects this in the about section showing premium.

It was after this that external access suddenly stopped.

Any help suggestions.....appriciated.

rgds Esh

[GJ51]

I've checked the port forwarding and both 4040 and 443 are forwarded correctly, although when checking with a port checker it only ever shows 4040 as open.

Think about it.

[Eshezo]

Thanks for a cryptic note "think about it"..... what I meant by that comment is that the ports are forwarded correctly on my router, I know that it would seem not the case if a port scanner is only showing port 404 open but then it will only show a port as open when the subsonic service is running.

So..... scenario 1/

Subsonic not running
portscan 4040 and 443, both show as closed

scenario 2/

Subsonic running
portscan 4040 and 443, port 4040 shows as open, 443 as closed

I've checked my router forwarding and had all firewalls turned off but still the same.

It would seem that subsonic is not responding to port 443 rather than the port not being forwarded

Been working on it for 3 hours now and no success

[GJ51]

Can you access Subsonic internally on port 443?

e.g. https://192.168.125:443

Does the internal connection convert to https if you attempt to use the vanity name? A common mistake is to try using https when entering the vanity name. That doesn't work. You have to use http to connect to subsonic.org - once the connection is made over http, subsonic will respond over https if you have it set up.

[Eshezo]

Can you access Subsonic internally on port 443?

e.g. https://192.168.125:443

Does the internal connection convert to https if you attempt to use the vanity name? A common mistake is to try using https when entering the vanity name. That doesn't work. You have to use http to connect to subsonic.org - once the connection is made over http, subsonic will respond over https if you have it set up.

HI, just tried this and:

tried on the LAN with "https://192.168.1.xx:443" and it works fine, when I try externally with http://xxxx.subsonic.org it immediately converts to https://xxx.xxx.xxx.xx:443 and dopesn;t connect.

I've tried "http://xxx.xxx.xxx.xx and it converts to just xxx.xxx.xxx.xx and doesn't connect, also tried http://xxx.xxx.xxx.xx:4040" and it converts to https:/xxx.xxx.xxx.xx and doesn;t connect.

Any further help out there would be much appriciated.

rdgs

[GJ51]

Re-check the port fwd rule for 443. If it connects internally but not externally then either the port fwd rule or the firewall on the host machine are not set properly.

Check the firewall to ensure that 443 is open on "All" network connections.

99% of the time this is due to a minor error in the port fwd rule. Double check that the rule for 443 is identical to 4040 with the exception of the port number. Verify that the internal address of the host machine is correct.

This is a common problem. You are not the first poster to claim 100% that the firewall is set properly - but it doesn't work. The bottom line is that if you can't see the port as open from canyouseeme.org, then you can't make the connection.

What happens if you attempt to connect from outside using https://EXTERNAL_IP:443 ?

If it works using the internal ip : 443 but not the external then something is blocking the connection. It can only be the router or the local firewall.