Subsonic Forum

Hello Sindre!

Decided to try your new Windows Installer version of Subsonic, so I completely removed the old Apache Tomcat + subsonic version and installed the very latest WIndows installer version.

After having started Subsonic, and waited for quite a while, the Subsonic icon finally appears in the systray, but on closer inspection it shows the following error message:

java.io.IOException: unable to establish loopback connection

Any idea of what could be causing that?

The first thing which comes to my mind is firewall issues related to loopback connection estasblishment. I am running Comodo Personal Firewall (www.comodo.com ).

IF i do need to explicitly define more advanced firewall rules for letting Subsonic establish a connection to the loopback interface what windows process should this be associated with?

(I am currently running the Comodo Firewall in a mode where I should be explicitly asked when a connection attempt is made for which there are no explicit firewall rules - but I do not get any such question )


PS: We miss you here in CoS

Hi Vidar, nice to hear from you again!

I haven't seen or heard about this error before, but searching the Java forums (e.g., this thread), I believe it's related to the combination of Java NIO and firewalls. For further diagnosis, I recommend temporarilty stopping the Comodo firewall and see if the problem persists.

If you need to define an explicit rule, the process in question is c:\program files\subsonic\subsonic.exe

Please update us on your findings.

Thanks,
Sindre

Hi,

I've just had this error and creating a new rule in Comodo did the trick.

Thanks.

I don't run comodo, and I have the same issue. Win7 x64, latest subsonic. Seems related to this guy's post
http://forum.subsonic.org/forum/viewtop ... 3511#23511

I have exactly this problem but only when Windows 7 x64 starts. If I stop the service and start, then it works. Any idea? Thank you.

I solved this problem adding subsonic_service.exe to trusted aplications in my Firewall (Commodo over Windows 7 x64). Thanks.

I run Subsonic (And other web serving software) on an old Windows XP Pro PC (Why throw it on the scrap heap when it will quite happily sit in a corner taking care of business while I do other things on other devices...) and hit this problem after a clean reinstall. Having tried various suggestions made around the forum, I finally came across this thread and gave the Comodo ruleset thing a try - but nothing I did would cure the problem.

However, I have had in the past, a couple of hiccups whereby the windows firewall had mysteriously turned itself back on blocking subsonic and also remembered I had installed Comodo previously sometime after I had been using Subsonic, so decided to come at the problem the other way and the solution I found was to:-

1) Uninstall Comodo to see if that was the problem - and indeed it was.

2) Reactivated Windows Firewall to make sure Subsonic had the relevant permissions there and once working THEN reinstalled Comodo and waited ready to pounce when the Comodo popup window appeared warning about Subsonic.exe - clicked "Don't isolate it again"

Will probably need to keep an eye on the situation for a little while longer but so far all now seems to be running as it should - even though this solution may seem like a sledgehammer cracking a nut!

It may also be worth noting here that after the reinstall I switched on HIPS for the 1st time in "Clean Computer" mode and now have it disabled. Once everything has settled down I may try turning HIPS back on and see what that does - If there is any issue with it I will add to this post. Meanwhile, if you have HIPS activated you might want to try disabling that before trying my solution.

***UPDATE*** Still not tried the HPS thing yet but I have just installed a new router and this caused Comodo to create a new network ruleset. As a result the IOException re-appeared yet again. Going to Comodo > Advanced Settings > Firewall > Rulesets > FTP Client > Allow outgoing DNS Requests and changing Dierection from "Out" to "In or Out" fixed the problem this time. Whether this is a good thing to do I don't really know - I'm just happy Subsonic is working again right now. It may also have been the problem all along and might have saved me doing all the above.