Subsonic Forum

as to why this is happening when I try to connect to my subsonic.org

"zzzz.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)"

I've been using this for years and this has periodically happened for short periods but it's been two days now.

THANK YOU and Happy Holidays

Check your server IP (make sure it is still fixed to the same as your opened port on router), then check your Wan IP with canyouseeme.org for your port number. If those check out okay, all you can really do is 'force-update' in settings by clicking Save under 'Access your server over the Internet using an easy-to-remember address.' Ensure that box was checked. Still, I've had it go a few days as well after I've done a router reset, and gotten a new Wan IP from ISP.

Thank you Alpha, I have done all that and I did do a router reset on Friday night, so that may be the culprit and I will just need to have some patience.

MM

Mike Marrone wrote:Thank you Alpha, I have done all that and I did do a router reset on Friday night, so that may be the culprit and I will just need to have some patience.

MM

You're welcome! It's one of those unexplained mysteries why the change takes a while to register. My log indicates a near-hourly port check by Network Service, so I suspect it has to do with DNS propagation or something? Oh well..report back if it doesn't self-heal.

It's been driving me crazy, which is not a very far ride. Subsonic's IP 169.mm.mm.mm:88
While my machine IP is 174.mm.m.mm

Is this what the holdup is? Waiting for the IP's to get in line?

Mike Marrone wrote:It's been driving me crazy, which is not a very far ride. Subsonic's IP 169.mm.mm.mm:88
While my machine IP is 174.mm.m.mm

Is this what the holdup is? Waiting for the IP's to get in line?

That's odd..169.x is usually a windows default when no dhcp contact was established. Also odd is your 174.x server addy..typically dhcp assigns a 192.x or a 10.x addy to lan clients.