Subsonic Forum

Problem Description: I'm currently running Subsonic from a Raspberry Pi, model B, and after the Wifi dongle started failing I switched it over to ethernet cable connected directly to my router. After doing so I could access subsonic on my home network just fine, but could not do so once I was connecting from outside of it.

Troubleshooting Steps:
1. Went into my router (Pace Plc 5268AC via AT&T Uverse) and located the raspberry pi connected via ethernet cable and set up Port Forwarding per the instructions here: https://portforward.com/pace-plc/5268ac/
2. Rebooted Raspberry Pi.
3. Edited the Raspberry Pi's configuration file to ensure that the static IP address had remained as such. Here's what I see in my ifconfig, IP routing table, and configuration file:

Code: Select all

eth0

Link encap:Ethernet   HWaddr b8:27:eb:c9:2e:6f
inet addr:192.168.1.67 Bcast:192.168.1.0 Mask:255.255.255.0


Code: Select all

IP Routing Table (there's only one line)
Destination: 192.168.1.0 Gateway: 0.0.0.0 Genmask 255.255.255.0 Flags: U Metric: 0 Ref: 0 Use Iface: 0 eth0


Code: Select all

auto lo
iface lo inet loopback
address 192.168.1.67
netmask 255.255.255.0
network 192.168.1.255
broadcast 192.168.1.0
gateway 0.0.0.0

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface defaul inet dhcp


Hardware Platform: Raspberry Pi Model B

Any help you can provide would be very appreciated.

I'd be interested to see screenshots of ifconfig and your router's port forward page. Also what the address resolves to when you try to reach it from an external network.

ifconfig:
https://www.dropbox.com/s/t5ht0ae9z3q6k5c/iconfig.jpg?dl=0

Router's Port Forwarding page:
https://www.dropbox.com/s/xx4rl2f7vsazcmt/router1.jpg?dl=0

And when I attempt to access the URL outside of my home network, I get a message that it's timed out, or that the server has stopped responding.

Delete the current portforwarding in your router and reboot it.
Configure either the Pi or your router so that the Pi always has the same ip addres.
Next configure your portforwarding again directing port 4040 to your Pi.
SInce you switched from wireless to wired lan the ip-address from the Pi has changed.

@toolman, thank you for the reply, however I've done as you suggested and I'm still not seeing any difference. I had already assigned the Pi a static IP address when I originally set up the Subsonic server. The IP address you see in the ifconfig from my previous post is the same one located in the configuration file, pictured here:
https://www.dropbox.com/s/v31kwvc974qnsx2/2017-02-13%2011.28.23.jpg?dl=0

I've since rebooted my router, deleted the previous portforwarding information, and doublechecked (and redone) the Pi's configuration file, with no change in the end result.

Hi.
What does Subsonic tell you in Settings >> Network ?
Did you disable the automatic network configuration? ( I suggest you do that and not rely on Subsonic )
Have you registered a subsonic adress and if so what's the status?
If you did and the status is " Succesfully registered" you could try to visit http://www.downforeveryoneorjustme.com/
It will always say that your subsonic adress is online, but if you click on your domain name you will either get connected or get an error.
You could also visit http://www.t1shopper.com/tools/port-scan/ to check if port 4040 is open.

Why is the gateway defined as 0.0.0.0?
Your screenshot of the port-forward doesn't actually look like a port-forward, just an entry to surpass the built-in firewall. Are you sure there isn't a proper port-forward section to your router's interface? The fact that it doesn't have you define the internal IP that port 4040 is being directed to is just...fishy.

Your issues are being caused by the crappy ATT gateway, IMO.

Edit: On second look: It seems your port forward page is one of those where you can select a device on the network? I hate those. I'd bet it's routing by MAC, or at least that "unknowndevice" object identifier is the MAC. So if that port forward entry remains from when the Pi was on WiFi, it's not routing to the ethernet interface regardless of if the IP stayed the same.

@toolman,

I don't have 'automatically configure' enabled. The error message for my registered subsonic address status is:

Failed to register web address. Network is unreachable (SocketException)

Subsonic can't reach the internet and hence you can't reach subsonic from outside your Home network.
So either the network-configuration of your Pi is incorrect, or your router blocks Subsonic from accessing the internet.
I would reconfigure both devices from scratch to avoid overlooking an obvious mistake.