Subsonic does NOT work inside a LAN

[usalabs]

After downloading and installing the rpm (OpenSuSe 11.4), by default, subsonic should (which is doesn't), listen on all network devices using 0.0.0.0 on port 4040, but before anyone says about firewalls and routers, there is NO firewall on my home server (running OpenSuSe 11.4), and all incoming from the WAN to the LAN IP for that server is blocked as is the WAN to the LAN IP to my workstation, blocking incoming to the server from the WAN stops access while the server , and it's software, is being tested locally on the LAN, now, every aspect of my server is accessible from the LAN, apache, webmin, phpmysql, PuTTY (using ssh), now here's the kicker, starting subsonic should, in theory, be accessible from any LAN computer using the servers LAN IP address followed by the port, in this case 4040.

Before anyone says about routers and port forwading, don't!, if it'll work on the LAN then it'll work when the port is forwarded, that's how I tested all my server software first, on the LAN, before forwarding the right ports.

So, back to subsonic, it seems, subsonic will ONLY work on localhost or 127.0.0.1, it will NOT work using the serevrs LAN IP address, EG:-

I start subsonic at the command line using root access:- ./etc/init.d/subsonic start
it tells me it's started and showing the PID and the log file name.

ps aux | grep subsonic shows the default setting for Host=0.0.0.0 and port=4040

on my workstation I open a browser, either IE, FF or Chrome, and enter:- http://192.168.0.100:4040 and after about 1 minute I get a time out,

on my workstation I open NX client and start a desktop session with the server, and in that session I start FF and enter:- http://127.0.0.1:4040 and get the subsonic login.

This all tells me that subsonic will NOT work when accessed outside the servers localhost.

As I mentioned earlier, forget about firewalls and routers, if all my other server software is accessible from my workstation without forwarding any ports on the router, just by using the servers LAN IP address, then subsonic should also work too,,,,too bad, it looks like I may have to use MediaTomb instead.

[ootuoyetahi]

Your router might not have a firewall (although I find this hard to believe) but your server does.

You can turn the firewall off in OpenSuSe by typing:

Code: Select all

/sbin/SuSEfirewall2 off

[usalabs]

Your router might not have a firewall (although I find this hard to believe) but your server does.

You can turn the firewall off in OpenSuSe by typing:

Code: Select all

/sbin/SuSEfirewall2 off

As I mentioned in my original post, my server does NOT have a firewall, I did NOT install one, neither firestarter or iptables, or even the Linux firewall, none of the firewalls are installed on my server, and that is why my server is not yet open to WAN access via the router.

I didn't say my router didn't have a firewall, the routers firewall/port forwading has nothing to do with internal LAN access.

I'll explain again, all my server (which has been running for 3 years) stuff can be accessed via the servers static LAN IP, which is 192.168.0.100, I've been using webmin, PuTTY, and web site access for a very long time with complete success, which means my server is NOT mis-configured, for some reason it's subsonic that is not behaving itself.

I can access all of my websites on the server using these:-

http://192.168.0.100 for the main site
http://192.168.0.100/media for image slideshows
http://192.168.0.100/downloads for file sharing
etc etc, and the all work, but it's subsonic that doesn't.

I even opened port 80 on the router and used my domain name to test access, and yes, it all worked from outside the LAN, so, if I can get subsonic to work inside the LAN successfully, then I can forward port 4040 in the router, and use my domain name to access it, but until then, subsonic will NOT work inside the LAN, ie, http://192.168.0.100:4040 on my workstation does NOT work, but using http://127.0.0.1:4040 on the server, it does work.

[ootuoyetahi]

First off, whether you installed a firewall or not, by default there is one installed and turned on in OpenSuSe. The fact that you can access it from http://localhost:4040 and not from another workstation on the lan says something is blocking it. Are you using Tomcat or Jetty as your webserver? Can you get to the default landing page?

[usalabs]

Well to satisfy your curiosity, the result of issuing:-

/sbin/SuSEfirewall2 off

results in this:-

bash: /sbin/SuSEfirewall2: No such file or directory

meaning there is NO firewall, and to show this, I used shieldsup from grc.com which shows either green=blocked, blue=closed and red=open

and even with the server temporarily set in the router DMZ shieldsup showed no green on any ports which means NONE of the 1024 ports commonly used are blocked, I also check on the default subsonic 4040 and that too is NOT green, it's blue meaning it's open, but nothing is listening on it,,,, it would be red if subsonic was listening on that port, hence NO firewall on the server, which will show green areas on the port grid. So, it's back to the drawing board yet again.

No I'm not using Tomcat, or Jetty, I'm using Apache, and yes, from any computer on the LAN, I can access every page that Apache is hosting, and, since I installed and setup the server, I've used SSH on an uncommon port to which I never had to allow through any firewall, I just set SSHd to use that port, and set the port in PuTTY and BAM! access to my server from the LAN.

Subsonic is the ONLY software that can't be accessed from outside the servers localhost, every thing I have on the server (that is accessible) can be accessed from within the LAN, such as apache, (not using default port 80), ftp (not using default port 21), SSH (not using default port 22), webmin (on default port 10000), so if all that can be accessed from within the LAN (and I didn't add any of it to any firewalls), then subsonic (by default) should be able to be accessed from within the LAN on it's IP and default 4040 port.

NOTE:
The server also runs opensim 3D virtual worlds regions which use ports 9000 to 9100, and that too can be accessed via it's client on the LAN, and without setting anything in a firewall, all I did was to forward those ports in the router and other people can access those regions too from their client software, also those region instances use the same host=0.0.0.0 to listen on all network devices, and that works, but subsonics host=0.0.0.0 doesn't.

[ootuoyetahi]

I dont know what to tell you, and these forums are dead. The only other thing I can think of that would make sense is that you dont have the files in the root of wwwroot and that you have them in a subfolder such as wwwroot/subsonic (which is how mine is set up). So you would have to go to http://<IP>:<port>/subsonic (for example). I am assuming you thought of this though and I cant think of a logical reason for this other than what has already been discussed.

[usalabs]

I installed subsonic using the rpm downloaded from this site, which installs its startup script at /etc/init.d and it's startup parameters at /etc/sysconfig and its main files are installed at /usr/share/subsonic containing the jar, sh and war files

netstat -a | egrep 'proto|LISTEN' doesn't show that port 4040 is being listened on, the only ports shown are 80, 443, 21, 10000, and 14022 is all that's listening.


NOTE:
I fixed it, by playing with the --port= argument in /etc/sysconfig/subsonic, and found out I had to use a high port, for some reason 4040 is not allowed, so I tried various other ports, and found I could use port 11000, and it worked.