Page 1 of 1

are we still having server issues?

PostPosted: Thu Feb 14, 2013 4:10 pm
by jonsaddles
Hi folks,
My SS server has been down for a while but have just found time to transfer it on to another machine and am having trouble accessing it.
Keep getting the error connection timed out and when I've gone back into network settings and asked it to check the easy-to-remember-address I get "Status jonsmusicserver.subsonic.org is registered. but could not connect to it. (ConnectionTimedoutException)
Pretty sure I've got the port forwarding setup correctly, at least the router shows a forward to the machine on the correct port, using a rasp pi so no firewall to turn off (that I'm aware of?)
Any advice would be very much appreciated.
Cheers
Jon

Re: are we still having server issues?

PostPosted: Thu Feb 14, 2013 4:24 pm
by bushman4
jonsaddles wrote:Pretty sure I've got the port forwarding setup correctly...


I'd say that is the problem... double check that the new computer is using the IP address that the router is forwarding to.

A local firewall would be the problem is you also cannot access it from your local network. But if the issue is only external access, the problem has to be port forwarding.

Glenn

Re: are we still having server issues?

PostPosted: Thu Feb 14, 2013 8:28 pm
by jonsaddles
Yea thats what I thought but all I've done is take an existing functional setup and point it at a different computer.
Because that didn't work I deleted and recreated the port forward but still with no luck.
Have tried the can you see me website and that can't access either so it is def something to do with port forward or firewall but just can't find anything wrong.
Does anyone know if there is an oddity with the R-pi and incoming access, haven't found anything on the forums about built in firewalls or anything daft but I'm a complete linux noob so haven't a clue really?

Re: are we still having server issues?

PostPosted: Thu Feb 14, 2013 8:31 pm
by bushman4
Does it work on your local network via IP address and port?

If so, it is port forwarding that is the problem. If not, it is a local firewall that is the problem (or a misconfiguration, like thinking it is using one port but it is actually using another...)

Glenn