Subsonic Forum

I am running the .war implementation of Subsonic 4.4 of Ubuntu with Tomcat6. I am using https from this tutorial http://forum.subsonic.org/forum/viewtopic.php?t=4841


I have my server on a static local ip, I had run into this problem before and figured it was just something I screwed up, so I purged tomcat6 and reinstalled both tomcat6 and subconic. It appeared to work and I went to sleep for the night, in the AM it stopped working again!


Here is the symptom: my external ip routes traffic to the wrong local address. I have also completely reset my router and the problem remains. I use port 8080 for http and 8443 for https, forwarded from a static ip of 192.168.1.254 (my server). I am reasonably certain that this is correct, but at this point I'm stumped.

It appears to be a port forwarding issue. It sounds as if DHCP is overriding your configuration settings and giving the server a new internal ip. I usually set the ip address for the server, both as a static address in the router AND a manually configured address on the NIC settings at the server. If the server address is defined at both ends, there should be no problem. HTH

Do you happen to know where the file is to add this configuration in Tomcat6 on Ubuntu? I've tried looking around for it. Do I just change what is probably 127.0.0.1 to the local address I want?

Sorry. I'm a Windows only kinda guy. Router settings are specific to your individual router and you need to check that manual for setting reserved ip addresses for the server.

In Windows going to "Control Panel\Network and Internet\Network Connections" gets you to the menus for changing the NIC from auto obtain ip to setting the ip address manually. I don't think you need to change the local address, but you do need to find where Ubuntu sets the NIC configuration.

This may be helpful:

https://help.ubuntu.com/community/NetworkAdmin

https://help.ubuntu.com/community/Inter ... ionSharing

Thanks for the help anyways. I was unable to make it work with 4.4 so I've rolled back to 4.3, I wonder if this is some sort of bug? There is not much in the way of documentation for the https implementation.


Bahhh it's broken in 4.3 as well, oh well I guess no https for me!