Subsonic Forum

A few days ago, my MacPro started blocking Subsonic. In the SL firewall settings, I have Subsonic set to "allow incoming connections". Under the Network page of the Subsonic settings, my port forwarding looks good, but I get a ConnectTimeoutException when trying to connect with my registered address. Also, I have port 4040 forwarded on my Airport Extreme. When I go to canyouseeme.org, it times out when looking for port 4040. However, when I turn off my Firewall under System Preferences>Security, everything works fine - canyouseeme can see the port and Subsonic works like a charm

Also, canyouseeme sees all of the other ports that I have open when my firewall is on - just not 4040.

I've tried deleting and re-adding Subsonic's open firewall setting, I've tried deleting and re-forwarding port 4040 on my wireless router. I've also tried changing the port that Subsonic uses by editing the info.plist file. No matter what I change it to, it remains blocked by my firewall.

Also, I haven't performed any OS system updates in the past few weeks. I am currently running Subsonic 4.5.

Any thoughts would be much appreciated. Thanks!

I just noticed this post but not being an apple user (except cider ) I cannot help much
but have you set up your firewall to allow SS outgoing connections as well on port 4040.

Yes, my Mac firewall is set to allow outgoing connections for SS on port 4040. And port 4040 is open on my router. When I turn off my firewall, SS works great. When its on, nothing (even though SS shows up as being allowed outgoing connections in my firewall settings).

You need to allow INCOMING connections to port 4040 as well. Enabling outbound for Subsonic on port 4040 will allow subsonic to answer a request (although I think that normally happens at higher numbered ports anyway) but it is never getting the request because inbound connections are being blocked.

HTH,

Glenn

When you say I need to allow incoming connections, I assume that you're talking about the firewall, which is currently configured to allow SS in - but I still can't connect. However, I figured out a workaround: I turn off my firewall, start SS, then start firewall - and I'm in. For some reason my firewall isn't letting SS to connect, even though I've told it to let SS make incoming connections.

I think there is a bit of confusion here.
You need to open the PORT in the firewall not the program.
So if you are using 4040 for SS then that port has to be open for both incoming and outgoing connections.
Remember when you are accessing SS from another machine its the browser eg. chrome/safari that is trying to connect not SS.
I don't know how you configure the Mac firewall but in windows you have the option of allowing a program or opening a port.

Here's how it works on a Mac: you tell the firewall what to let in - everything else is blocked by default. When something tries to communicate out for the first time, the firewall asks you if you want to allow (in this case) Subsonic to "accept incoming connections". When you click "yes", SS shows up on a list of approved programs who can communicate with the outside world. Every other program I have on this list is working fine. And I already have port 4040 forwarded on my wireless router.

I've narrowed the problem down to my firewall. As I mentioned, everything works fine if I disable the firewall altogether, start Subsonic, then re-start the firewall. When I do this, I get the same message: "Do you want to allow Subsonic to accept incoming connections". I click yes and everything is fine. However, if my firewall is running, and I start Subsonic and click "yes" to the above question - no dice. I have to disable the firewall before starting SS, then re-start the firewall.

Any thoughts?

I would bypass the Application Firewall and use the ipfw that is running behind it to open the port.

"I'd recommend using WaterRoof to manage the firewall. It's a GUI frontend for dealing with ipfw (the FreeBSD sponsored open source firewall you have). For action, leave it as allow and for protocol use any. Set the IP addresses and port you want opened accordingly."

Taken from SuperUser.com

HTH,

Glenn

Hi,

I'm having the same exact problem as ikeldin. Does anyone have any advice? When the firewall is off subsonic works great. But once I turn on the Mac OS firewall, I am unable to connect to the server. Thanks in advance.

MandirnOrange wrote:Hi,

I'm having the same exact problem as ikeldin. Does anyone have any advice? When the firewall is off subsonic works great. But once I turn on the Mac OS firewall, I am unable to connect to the server. Thanks in advance.

I'm resurrecting an older post in hopes of finding a solution. I'm having he identical problem, even with Subsonic added to the firewall as an exception.

thx, Jack

jkstorer wrote:

MandirnOrange wrote:Hi,

I'm having the same exact problem as ikeldin. Does anyone have any advice? When the firewall is off subsonic works great. But once I turn on the Mac OS firewall, I am unable to connect to the server. Thanks in advance.

I'm resurrecting an older post in hopes of finding a solution. I'm having he identical problem, even with Subsonic added to the firewall as an exception.

thx, Jack

Did you create an exception for all ports Subsonic is using? ie, the HTTP port and also the SSL port if you are using it?

Or did you create some kind of "application" exception?

I would create port exceptions if you have the choice... but I'm not a mac guy, so I can't give specifics.

Glenn

bushman4 wrote:

jkstorer wrote:

MandirnOrange wrote:Hi,

I'm having the same exact problem as ikeldin. Does anyone have any advice? When the firewall is off subsonic works great. But once I turn on the Mac OS firewall, I am unable to connect to the server. Thanks in advance.

I'm resurrecting an older post in hopes of finding a solution. I'm having he identical problem, even with Subsonic added to the firewall as an exception.

thx, Jack

Did you create an exception for all ports Subsonic is using? ie, the HTTP port and also the SSL port if you are using it?

Or did you create some kind of "application" exception?

I would create port exceptions if you have the choice... but I'm not a mac guy, so I can't give specifics.

Glenn

Glenn, I've only created an application exception using the OSX interface to the firewall.

There are some 3rd party app's that let you manage the underlying ipfw firewall such as WaterRoof, but it's not very intuitive to the casual user. Would be great for someone to post a more detailed how-to for us dummies.

I tried adding the following rule using WaterRoof

g]

the firewall logfile shows the following after I save my network settings in Subsonic and it tests the connectivity:

Apr 8 16:42:10 jaxmac.home socketfilterfw[98] <Info>: Deny JavaApplicationS connecting from 66.49.215.227:41753 to port 4040 proto=6

And BTW, I'm using Mountain Lion (10.8 ) now, but I've been having this issue since installing Snow Leopard