Subsonic Forum

I switched to HTTPS access (port 443) on my home Subsonic server today after using it unsecured for years without a hitch. When I tried to access my library at work, I find that it causes Firefox to hang. More specifically, it causes the "Plugin Manager for Firefox" process to run away, eating up more and more memory until I kill it. Once killed, Firefox notifies me that the Adobe Flash plugin has crashed. I've tried restarting FF with add-ons disabled in case one of them was the culprit with no success. HTTPS access works fine in IE, but I don't want to switch browsers, nor do I want to go back to an unsecured connection.
Here's a sample of the log for a song successfully played under IE:

Code: Select all

[4/3/12 4:22:57 PM MDT]    INFO   PlaylistInputStream   srobison13 listening to "2009 - Ellipse\11 The Fire.mp3"
[4/3/12 4:22:57 PM MDT]    DEBUG   TranscodeInputStream   Starting transcoder: [c:\subsonic\transcode\lame] [-S] [-h] [--resample] [44.1] [-b] [96] [--tt] [The Fire] [--ta] [Imogen Heap] [--tl] [Ellipse] [E:\My Music\Imogen Heap\Releases\2009 - Ellipse\11 The Fire.mp3] [-]
[4/3/12 4:22:58 PM MDT]    DEBUG   AudioScrobblerService   Successfully registered now playing for song 'The Fire' for user stooka at Last.fm.
[4/3/12 4:23:32 PM MDT]    DEBUG   AudioScrobblerService   Successfully registered submission for song 'The Fire' for user stooka at Last.fm.

And here it is when it hangs Firefox:

Code: Select all

[4/3/12 6:22:54 PM MDT]    INFO   PlaylistInputStream   srobison13 listening to "2009 - Ellipse\11 The Fire.mp3"
[4/3/12 6:22:54 PM MDT]    DEBUG   TranscodeInputStream   Starting transcoder: [c:\subsonic\transcode\lame] [-S] [-h] [--resample] [44.1] [-b] [96] [--tt] [The Fire] [--ta] [Imogen Heap] [--tl] [Ellipse] [E:\My Music\Imogen Heap\Releases\2009 - Ellipse\11 The Fire.mp3] [-]
[4/3/12 6:22:55 PM MDT]    DEBUG   AudioScrobblerService   Successfully registered now playing for song 'The Fire' for user stooka at Last.fm.
[4/3/12 6:23:14 PM MDT]    DEBUG   InputStreamReaderThread   (c:\subsonic\transcode\lame) Error writing mp3 output
[4/3/12 6:23:14 PM MDT]    DEBUG   AudioScrobblerService   Successfully registered submission for song 'The Fire' for user stooka at Last.fm.

Does anyone have any advice? Thanks

Try turning off SSL and testing again.
I had a similar problem with FF which I solved by un-installing the adobe flash plugin and re-installing.
That was using normal http so the https problem may be a "red herring"

I just tried doing a clean uninstall of Flash using Adobe's uninstall tool, then put a fresh copy back on. The same problem is still there. I'm at work now so I can't disable SSL. Thanks for the help.
One question I forgot to ask: Doesn't the failure in the log ("Error writing mp3 output") imply that the issue is on the server side, not with my client machine? If so, what difference could using a different browser make?
Any other ideas?

No ideas? File type doesn't seem to matter (.mp3, .ogg, .flac, etc.). I've resorted to using Chrome for listening, Firefox for everything else. This is not a good solution. Is there anything else I can do besides cross my fingers and hope the next release of FF fixes the issue?

Hey guys I've the same problem. I used to switch to https at port 8082 and at first everything was fine, but then I realized that video streaming with Firefox was impossible because every time I started to watch a video the flash plugin crashed and I had to restart Firefox (

I'd be really pleased if someone could give me some advice what to do.

Greets wannabe_nerd

Just updated to FF12 - no change. I even tried running in "safe mode" with all extensions disabled again. Still working fine in other browsers. Come on Mozilla!

Never use 80 or 443 ports.

Use Chrome for Subsonic It looks great, nice and clean appearence and easy to setup for auto logon so you can just open your site in the browser without even seeing the logon screen. It's also fast loading and responsive and never has an issue with flash for video.

HTH

Why not use port 443? Because it's a "known" port which malicious people will be looking for?

srobison13 wrote:Why not use port 443?

Because its a standard port (like 80) which is used by any outgoing traffic on the server pc that requires ssl.
If you use 80 or 443 for subsonic then NO other programs must use those ports or you will get conflicts.

The next release will not use port 80 on Windows as the default. I'm not sure about the SSL port but I think we can get that changed pretty easily as well. I don't know what the other versions use for the SSL. Anybody know what the default SSL port is on the Linux version?

GJ51 wrote:The next release will not use port 80 on Windows as the default. I'm not sure about the SSL port but I think we can get that changed pretty easily as well. I don't know what the other versions use for the SSL. Anybody know what the default SSL port is on the Linux version?

I saw you posted something in another thread about having to tell everyone to not use port 80 or 443. What's the reasoning? Are people really running other web servers or applications as well that use those ports? It seems like common sense that you can't run more than one service on the same port. Is that the only reason the ports are changing?

80 and 443 are great, you don't have to tell someone a port when you tell them your site. Just don't run other sites unless you've got more IP's.

It's not that 80 and 443 WON'T work, it's just that we were seeing more and more users that were running into conflicts using the standard ports. WHS uses them by default for their remote access setup and many Windows installs were being done on WHS.

It's not as common now, but back when we first atarted troubleshooting the install problems it was actually common for ISP's to actually block 80 and 443 to prevent residential users from hosting websites. Believe it or not most ISP contracts still have clauses that residential users aren't supposed to host websites, but I haven't heard of any recent enforcement of the issue even though it's still a clause in most agreements.

It just became easier over time to eliminate the default ports as the potential for conflict was very high. By telling everyone who was having trouble to switch off the standard ports, we didn't have to get into troubleshooting everyones individual setup to get them up and running.

In short - we just followed the path of the least resistance.

By not using the standard ports, it also helps avoid problems down the road if a user installs something else latter that tries to use the same ports in its default setup.

The last I heard was that 4.7 will be using 4040, and 4443 for SSL on the new Windows setup. Of course these will just be new defaults, you'll always be able to switch to 80/443 if it works on your network.

Got it...path of least resistance. Coming from the vortex of confusion that is IT support I can get with that. Just making sure I wasn't missing something.

Thanks.

I tried switching to another port for ssl today - same results: works in other browsers, hangs Firefox. I also tried Firefox under Ubuntu in VirtualBox and it didn't work either. Chrome it is I suppose.

Subsonic LOOKS and works fabulous in Chrome. Nice clean appearence and very responsive. Each tab is a shortcut with the credentials already set for instant logon making it easy to switch between sites without having to reenter u/p every time.