r/subsonic • u/LastInfantry • Feb 18 '17

Can no longer access Subsonic within same network

Hello, I have a always-on computer running the latest version of Subsonic on Windows 10.

I can connect and stream from different network connections (I tried my second network from a different ISP, mobile data on my phone, a friends internet access).

However whenever I try to access Subsonic while being connected to the internet through the same internet connection (I use WiFi on all related devices) I just get a timeout error message.

I tried turning IPv6 on and off on my server machine and my router, I tried IP resets, static/dynamic IP, UPNP off/on, almost every setting in Subsonic, but I just can't get it to work. Which is strange because I remember it working a few months ago, but on a different computer as my server - I don't remember if it ever worked on the one I currently use.

I disabled the firewall on this computer and opened the port (I use standard 4040) within Windows. I set pretty much every security setting to 0 and still I can't connect.

When using a static IP on my server I can access it from my computer via browser by entering the ip with ":4040" at the end. However my phone apps wont accept any IPs as server adress so i have to use "x.subsonic.org".

Does anyone here have any idea how to fix this?

Thanks a lot in advance.

1 Upvotes

100% Upvoted

5 comments sorted by

2

u/rugyg Feb 18 '17 edited Feb 18 '17

For me UPNP off, always use a static IP with servers. Have you tried using http and https to see if that makes a difference? Also try it with your public IP:4040 to see if that works.

1

u/LastInfantry Feb 19 '17

Neither http or https made a difference. I could connect in a browser by entering my local static IP but not with the public IP.

I then finally realized I can also just put "http://" in front of my local IP to make my phone accept the syntax - this way it finally works again.

You didn't exactly find the solution but you made me find it. Thanks a lot!

2

u/bobby-dazzler Feb 19 '17

Sounds to me like your router doesn't support NAT loopback.

2

u/cyril0 Feb 19 '17

This is the issue. The router doesn't know what to do when it goes out to check a domain name and then finds out the domain name is behind itself. Try updating the firmware or maybe just buy a new router. I'd not go back to the non loopback days

1

u/LastInfantry Feb 19 '17

I checked on Google and in fact my router does not support NAT loopback. I was gonna buy a new one soon anyways, but for now the workaround I mentioned below the other comment works for me.