Subsonic Forum

Just moved to a new ISP, so my IP changed and it looks as though the sub-domain is pointing elsewhere.

Is this a support issue or can I re-submit through the admin console?

I try to save my current settings to reset the address, but I get this error.

Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding).

If your router can't be configured automatically you can set it up manually. Follow the instructions on portforward.com. You must forward port 8080 to the computer running the Subsonic server.

Status: Successfully forwarding port 8080.

Access your server over the Internet using an easy-to-remember address.

http://.subsonic.org

Status: alreadyfried.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)

alreadyfried wrote:Just moved to a new ISP, so my IP changed and it looks as though the sub-domain is pointing elsewhere.

Is this a support issue or can I re-submit through the admin console?

I try to save my current settings to reset the address, but I get this error.

Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding).

If your router can't be configured automatically you can set it up manually. Follow the instructions on portforward.com. You must forward port 8080 to the computer running the Subsonic server.

Status: Successfully forwarding port 8080.

Access your server over the Internet using an easy-to-remember address.

http://.subsonic.org

Status: alreadyfried.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)

So long as you are successfully porting (see Status above), it will eventually sort itself out, once Subsonic 'phones home' to update your new IP.

alphawave7 wrote:

alreadyfried wrote:Just moved to a new ISP, so my IP changed and it looks as though the sub-domain is pointing elsewhere.

Is this a support issue or can I re-submit through the admin console?

I try to save my current settings to reset the address, but I get this error.

Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding).

If your router can't be configured automatically you can set it up manually. Follow the instructions on portforward.com. You must forward port 8080 to the computer running the Subsonic server.

Status: Successfully forwarding port 8080.

Access your server over the Internet using an easy-to-remember address.

http://.subsonic.org

Status: alreadyfried.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)

So long as you are successfully porting (see Status above), it will eventually sort itself out, once Subsonic 'phones home' to update your new IP.

I guess 6 months isn't long enough for it to sort itself out, then.

I've not really pushed the issue until now, but it would be nice to access my tunes from work or the phone...

Right now, I'm getting a 97.74.x.x ip when I try to resolve my name.subsonic.org url....my actual ip address is a 174.70.x.x ip.

Any quick way to re-register my url's DNS entry to my new ip....I actually don't think i've ever had a 97.74.x.x ip address...looks like it is based out of Arizona and I'm in Louisiana...

hmmmm

Just a hunch, but I bet if you went into the SS control panel and changed the port number, which also means you'd have to chage the forwarding on the router, it would force it to update the SS.org server.

EDIT: On second thought, you might be able to change the port number on the server, do a stop/start, thern just change it back to the original port number and do another stop/start, without changing the router settings.

It is also possible that the router is not set up properly now, which could be the source of the problem.

GJ51 wrote:Just a hunch, but I bet if you went into the SS control panel and changed the port number, which also means you'd have to chage the forwarding on the router, it would force it to update the SS.org server.

EDIT: On second thought, you might be able to change the port number on the server, do a stop/start, thern just change it back to the original port number and do another stop/start, without changing the router settings.

It is also possible that the router is not set up properly now, which could be the source of the problem.

Yep..and the log will indicate a successful update or fail.

Ok, well apparently the issue lies in the router....who woulda thought, huh?

For some reason the new ports added (8080,4040,4041,etc...) are not forwarding correctly....

So just for giggles I tried an existing port I already have forwarded....3389 - RDP & 5900 - VNC....and Voila!


No probs when I change my subsonic port to either on of those and kill the RDP/VNC services...

So, thanks for the responses...I will now take my router out back and use it as target practice.

I do have WWDRT firmware on my router, so there could be some variables within there that I haven't discovered and may be causing my port forwarding issues.

Thanks, again!

hmmm that's odd. What version of dd-wrt are you running? If it is less than v24 I would do a firmware flash before you throw out your router if you are running anything below v24.

kermit22 wrote:hmmm that's odd. What version of dd-wrt are you running? If it is less than v24 I would do a firmware flash before you throw out your router if you are running anything below v24.

Or do a full-on reset of the router, and start from scratch. The exact thing is happening to me right now: I was playing with Firefly Media server, added it's ports, and yet could not get the ports to forward at all. THEN I noticed I could not access SS either, so those ports were hosed somehow during the Firefly set up. I tried re-adding the SS port several times to no avail before giving up last night. This morning, I'm preparing to blow out all settings to factory state, and start over. /sigh

Just on a side note:

I've burned through quite a few routers, as they seem to degrade over time and start to fall apart after about 2 yrs. I recently replaced my last one with a Netgear WNDR3700. It's a bit pricey, $150 but so far it performs well and seems to run much cooler than the routers I've owned previously.

Running v23 sp3 on my gateway router....

I'll try upgrading firmware to see if that's the ticket...

I was only slightly kidding about trashing the router...I have a few laying around where I could dispose of it and still be in good shape...but its more of a "spare time" thing, than anything.

Thanks for the suggestions and input so far....