xxxxx.subsonic.org is registered, but could not connect to

[syspike]

Hi I recently had to reinstall subsonic. For the last 3 days I keep running into the following error message

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

The above error is preventing me from connecting to my subsonic through the internet via my iphone or through a browser session
I've researched this forum and found several other folks reporting similar issues but I don't necessarily see a resolution.
I believe I have correctly set up the port forwarding rules, still nothing. When I ping the subsonic URL I generally get the IP address of the subsonic servers in CANADA or wherever they are. I know I should be getting my assigned external ISP provided IP... is there a way to manually test that its not just a subsonic server backend issue....
Also can you use subsonic without this "vanity url" - I've read that this URL or your ISP assigned IP must be registered with the subsonic ssl redirect servers.
appreciate any insight anyone can provide.

[gurutech]

Did you reisntall on the same computer, or a different one? You will need to change the port forwarding on your router if this is a new machine, as the internal IP address will have changed.

Also make sure that you aren't trying to go to the *.subsonic.org address from within your own network on a machine that's not the server. For some reason, there's a DNS issue somewhere that causes all non-subsonic server computers on the same LAN as the server to be translated as the local machine you are on, not to the machine that's running subsonic. The "fix" for this is to get your own DynDNS or No-IP account and use that instead of the *.subsonic.org address.

[syspike]

Hi gurutech,
I had to resintall on a new machine - its Ubuntu server. the port forward rules were updated.
I do have a dyndns account if I don't need to register with subsonic.org then I will use by own... I was under the impression it needed a subsonic suffix to work from the internet. thanks for the tips i'll see if I can try to get it to work following your suggestions.

[gurutech]

Make sure port 4040 is open on your Ubuntu firewall also.