Subsonic Forum

Problem Description: I've set Subsonic up, and have it working both using the web interface and iSub, using a *.subsonic.org address. However, I ran into problems with my ISP swapping my IP address around while I'm trying to stream from it, which obviously breaks everything a bit - so I decided to start using Dyndns to try and alleviate this and keep a static connection to my dynamic IP. However, after having set up a dyndns URL that forwards to my subsonic IP, I can't access subsonic using it. All that happens when I use dyndnsURL:port is that chrome downloads a download.file which contains a few non-displayable characters. I can still access subsonic both locally & using my external ip + port.
Troubleshooting Steps: Restarted computer/Dyndns/SS/iPhone/anything else I could think of. Chopped and changed ports/URLs. Nothing seemed to clear it
Playback Application and version: iSub/Web - but these are both working as expected.
Subsonic Version: 4.6.beta2 (build 2566) – November 16, 2011
Server Version: jetty-6.1.x, java 1.6.0_29, Windows 7 (65.4 MB / 96.7 MB)
Hardware Platform: Windows 7
Java Memory Limit: 100MB

You need to specify the port no unless you are using port 80.
The subsonic.org address takes care of that for you automatically.

I am specifying the port. If I just hit my dyndns URL, it can't connect, because obviously there's nothing there. If i hit dyndns URL:port I get this:

http://i.imgur.com/oz66A.png

Which when I open in Notepad shows this:

http://i.imgur.com/fMQUb.png

On iSub, trying to hit dyndnsURL:port gives me this error, which I believe means "there's no Subsonic here":

http://i.imgur.com/UMBPh.png


(I would've [img]'d these, but I can't figure out resizing)

Have you a context path set up in control panel? You will need to specify that as well if you have.
eg. dyndns_address:portno/context_path/
Also check that dyndns address has got the right IP address (I presume you have set that up in the router?)

There's no context path, no. And my dyndns address definitely resolves to my IP. It's not set up in the router, no - but I have manual port forwarding to my subsonic config. As far as I know, I don't need to do anything else in the router, as the dyndns address should behave exactly the same as just using my external IP. (which it isn't)

I have my dyndns address set up in the router so that it can keep it updated.
However as your subsonic.org address works and will keep itself updated automatically.
(which you can do manually -settings/network -hit save) I suggest you use that.

Why your dyndns address is not working I do not know (browser cache maybe?) but it is not really a SS issue.
Try the DynDNS forums http://forum.dyndnscommunity.com/forum/

Ah yeah I have the Dyndns software running on my laptop to keep it updated, rather than on the router.

And yes, the subsonic address works - my only issue is that it doesn't seem to be updating fast enough, resulting in considerable downtime when my dynamic IP changes. I can't manually update it when I'm streaming using iSub, either, because I can't log in to it, due to my external IP having changed.

Also, I'm pretty sure this is a SS issue, what else could be returning the special characters? Dyndns is working as expected, I can resolve that address to my IP.


Having said all of those, my dynamic IP doesn't seem to be changing as often as it did yesterday... Perhaps I'll be okay. I'd still appreciate any help you can offer about this though - the dyndns URL offers 20sec updating, which is obviously preferable to the speed of the *.subsonic.org address.

I have no idea how often SS updates the subsonic.org address but I doubt if it is as often as that.
Perhaps someone else could enlighten us
With regard to the dyndns address what happens if you use your external IP address (+port no)
And before you answer, yes it should be the same, but this is a computer we are talking about

What are you using for a firewall?

Ooooooooh! I just found out some more weirdness. Okay so... I have force https set to port 23141, and obviously just http on port 23140. If I try and do external IP:23141 OR dyndns:23141, I get that error. BUT if I do external IP:23140, it redirects me to the https address and... works. Both ports are forwarded in my router. I guess this is a sort-of fix, because I can just use the non-https port to connect and then get forced onto https, but I suppose this is still a bug?

@Extrace - Just the Windows one, I'm pretty sure SS has configured it itself.

That is exactly how it is supposed to work. If you have HTTPS set up you must hit the HTTP port and get redirected to the HTTPS port for it to work.

So yes, this is "by design."

Glenn