Subsonic Forum

I'm testing Subsonic with Cloudflare's SSL/Spdy, and noticed I kept losing spdy (according to the firefox indicator)

Seems spdy assumes its using http (its a mix of http/https requests), even when I asked for a https request.

http://i.imgur.com/IEIxq.jpg

Ideally Subsonic shouldnt assume http, it breaks spdy

I'm not that familiar with SPDY, but there are a couple things worth considering.

First, many users make the mistake of trying to access their sites using https directly with their server.subsonic.org address. This does not work as the setup is a redirect service, not a dns service. Always use the http://servername.subsonic,org address if that is how you are attempting to connect. Once the request is received at the server it will then use SSL if it is enabled on the server.

Second, isn't SPDY a Google/Chrome protocol? Have you tried the same scenario using Chrome?

I personally prefer using Chrome with SS as it runs very well, looks very clean and is very easy to set up shortcuts that auto logon to the various SS sites that I visit.

HTH

Hi,

Long time user. Just finished rebuilding my setup, using Windows 7 this time instead of Ubuntu. I want to get SSL up and running. Am I correct in assuming that if I click on the Subsonic control panel in Windows and enabled https on port 4443. I also port forwarded 4443 (in addition to 4040) on my router.

In order to use SSL and HTTPS, I still log-in to http://username.subsonic.org...and use this when I log-in on Android, or iOs. But, even though I am using http...and not https...I'm still using SSL and secure?

Just trying to make sure I'm doing as much as possible to lock it up. Thanks in advance.
-Ian

In addition, I logged in under http://username.... on another computer, and in Chrome it is listing the page as using SSL, but having a high risk...it's got the red slash through it.

https://support.google.com/chrome/bin/a ... _indicator

Thanks in advance.

Yes. You've got the right idea.

You get the warning because you are using SSL without a certificate. Most sites that use SSL purchase a certificate that registers the site as a known site. You can buy one and install if you like, but for most of us it's not worth paying for something that just removes the warning. You know what you are logging into and by doing it this way you still get the benefit of secure transmission of the data.

You're doing it right from what I can see from your description.

Thanks again Gary. It doesn't bother me that the warning shows up. I also tried logging in to the Android app using HTTPS...and it didn't recognize me at all. I guess sticking with the regular HTTP will work. I'm trying to set up Music Cabinet now...and then see how stable this thing is.

Thanks as always!!!

When you use the Subsonic redirect, you have to use the http address. Once that connects to your Subsonic server, the server will shift the connection to SSL. So when you input the address to make the initial connection you have to use the http://server.subsonic.org to connect whether it's on Android or any other browser.

You can make a direct https connection if you want to, but not using the subsonic.org address. If you want, you can just input your external ip:port# in the Android address and it will hook up directly to the SSL port. Likewise, if you typr your external ip:port# into any browser it will direct connect as well.

I think I might investigate the direct connect from mobile apps at some point. I made the jump to Music Cabinet and at least the Android app doesn't play nice with it. I think I'll spend some time cleaning up my tags again....and then just listening to music again.

Thanks again Gary.

Would you mind elaborating on the Android+MusicCabinet issues? It's supposed to expose the same REST interface as a Subsonic 4.6 server for mobile clients. I've only tested it with iSub though, I figured that should be enough, but maybe no?

Hey Hakko... Fancy meeting you here...

I was in the middle of posting on your thread when I figured out how to update Music Cabinet. Great work so far.

My issues so far tend to be cover art, mixing of different folders (music, comedy, audio books), and listing of random...last played... Newest... In the Android app. Of these I think most will come out in the wash...and with some tag edits. I plan on testing out iSub as well to see how it performs.

Great work overall. We'll be giving it a big test over the next couple of weeks. I would like to see an android (and iOs) app built to take advantage of all that your work can do.

Thanks again.

Please post error reports in the MusicCabinet thread (viewtopic.php?f=8&t=9504) if you run into any trouble with the Android client, with steps on how to reproduce.

Be sure to use the latest version (0.7.10), the early 0.7 versions had some issues with mobile clients, but as far as I know, those are fixed now.

The mixing of folders might persist though as the browsing is tag based, not folder based. That means your artist names are displayed in the interface, not your folder names. Cover art from last.fm that's used in the web interface is not used in the mobile clients, they only use embedded artwork / folder.jpg etc. If your library is horribly tagged, some files might be ignored by the media scanner (files lacking either artist or title tag) as the scanner has no way of knowing what music that actually is. Warnings about such files are written to musiccabinet.log during initial scanning.

Will do. I updated to the new version yesterday afternoon and it runs well on the Android app. The issues I had with sorting of albums (recently played, recently added) is gone...it works. I'm fixing metadata again as I need to clean up again after an ill-fated attempt to use an automated tagger.

Thanks again.