#199 Subsonic premium domains do not work when HTTP is disabled

[John Vilk]

I am a Subsonic Premium subscriber, and a huge fan of the software! Unfortunately, the current bug reduces the utility of my subscription.

Problem

When HTTP is disabled (port set to 0), the Subsonic Premium subdomain is set to the Subsonic server's local IP, and not its external IP.

Steps to Reproduce

1. Purchase Subsonic Premium.
2. Download the standalone version of Subsonic.
3. Configure Subsonic for HTTPS appropriately.
4. Manually port forward the HTTPS port. Verify that you can access Subsonic appropriately from an external network using your IP address.
5. Set -Dsubsonic.port to 0 to disable HTTP access. Subsonic should still function via https:// requests.
6. Go into Settings -> Network, and configure your Subsonic subdomain.
7. Observe that you receive the error "Status: Could not connect to xxx.subsonic.org. (HttpHostConnectException)". In addition, the subdomain will now forward to your server's internal IP (e.g. 192.168.1.xxx).

*People Affected

• Anyone who wants to disable HTTP access to their Subsonic server.
• The FreeBSD package for Subsonic-standalone recently changed to set the HTTP port of Subsonic to 0 when SSL is enabled, so this is a problem for all FreeBSD users that decide to enable SSL. There are no workarounds without modifying the package.

[John Vilk]

Ack, I am unable to edit the bug report to redact my Premium subdomain (it's in the error message in step 7). If you could remove that so it is not present in Google searches, I would appreciate it. :)

[Sindre Mehus]

Done :)

[John Vilk]

Also, I created a FreeBSD issue for the port configuration limitation.

[John Vilk]

Clarification: It appears that Subsonic does detect the external IP correctly. However, it unconditionally redirects to the HTTP port and not the HTTPS port.