Setting up https://myname.subsonic.org on non-standard ports

[russcasey]

I have my local subsonic installation running on port 8083 for http and 8084 for https. I need to use ports 80 and 443 for other services.

When I try to access https://myname.subsonic.org from the local machine, I get forwarded to https://192.168.1.77:8084/ which works.

When I try to access https://myname.subsonic.org from a machine on the internet, I get a 404.

Is there any solution to this that doesn't involve me reconfiguring to run subsonic on port 443?

[bushman4]

When you click on the link from outside, where does it redirect to? Is it http://YourExternalIP:8083?

If so and it still does not work then the traffic is being blocked somewhere, either by your ISP (doubtful), at your router/firewall (more likely) or at the server's firewall (unlikely, since you said it works from an internal client).

HTH,

Glenn

[russcasey]

From an external machine:

I can reach my subsonic install at https://[myexternalip]:8084/
I can reach my subsonic install at https://myname.dyndns-server.com:8084/
Requests to https://myname.subsonic.org:8084 break
Requests to https://myname.subsonic.org break
Requests to http://myname.subsonic.org are redirected to http://[myexternalip]:8083/, which is blocked by my firewall

[GJ51]

The redirection service done by ss.org is only reachable by http as you can see on the Settings/Network page where the ss.org access option does not allow you to edit the http://, but only insert your name. When you use the http://myname.subsonic.org address ss.org redirects the request to your external ip:port# via http. Subsonic then responds via ssl if you have it enabled. Because you are reaching the redirection service first when you use your ss.org name, you must use http.

There is no need to block 8083. If you forward 8083 to SS, it will respond to all requests from 8083 over ssl and establish the link over 8084. Openning 8083 will allow you to use the ss.org name.

[bushman4]

Yeah, what he said...

If you unblock the HTTP port everything should work right. It works like this:

• Your browser makes a request to Sindre's server for http://myname.subsonic.org. The server responds with a "302 - Temporarily Moved" message that includes your external HTTP access information of http://[myexternalip]:8083/
• Your browser contacts your subsonic server via that external IP address on the HTTP port. If HTTPS is set up properly, your subsonic replies with a "302 - Temporarily Moved" message that includes the proper external HTTPS access information of https://[myexternalip]:8084/
• Your browser contacts your subsonic server using HTTPS on the proper port. Subsonic replies with a "302 - Temporarily Moved" message again, but this time it includes the info to redirect to the login page at https://[myexternalip]:8084/login.view;jsessionid=<SomeSessionID>
• Your browser contacts your subsonic server using HTTPS and retrieves the login page.

As a demonstration of this, run the "Full Page Load Test" at pigdom.com and enter http://name.subsonic.org (once you have opened the HTTP port on your firewall) or download the command line tool wget.exe and run

Code: Select all

wget http://name.subsonic.org

Notice all of the redirects that happen in the process.

HTH,

Glenn