Connection refused (111) by Firewall ?

Read 7215 times
Hello Streamers!

Yesterday we have made a fresh install of Centos 6.3 with Centova 3.

24 hours later we run into the big problem (Connection refused (111)) as the most people in here.

We have opened a ticket and after many hours of conversation remain the question (Why ?).

The latest message from administration was : The log you sent does not show cc-control exiting. It shows it running normally. If you're still getting that error while it's running, then you have a firewall issue or something else that's preventing the Centova Cast web interface from connecting to 127.0.0.1 port 2198.

Our Firewall is OFF, iptables Disabled !

Anyone knows anything about it, how can we be OnAir ASAP ?

Thank you in advance for reading this, but if you know please answer...
24 hours later we run into the big problem (Connection refused (111)) as the most people in here.
Very few people actually encounter such an error...

We have opened a ticket and after many hours of conversation remain the question (Why ?).
Ticket ID?  It shouldn't take many hours of conversation to find out why.  It's pretty simple to diagnose, really, if you have root access to the server and a bit of sysadmin knowledge (or can provide us root access).

The log you sent does not show cc-control exiting. It shows it running normally. If you're still getting that error while it's running, then you have a firewall issue or something else that's preventing the Centova Cast web interface from connecting to 127.0.0.1 port 2198.
That sounds pretty much correct to me.  If cc-control is not exiting, then something is definitely stopping the web interface from connecting to it.  Could be a firewall, could be a networking issue, could be that you've modified the configuration files and changed some IP addresses in some places but not others.

Our Firewall is OFF, iptables Disabled !
Good to know, but the message does say "a firewall issue or something else that's preventing" the connection as opposed to "it can only be the firewall".

As a general rule, if the advice given by our helpdesk staff doesn't resolve the issue, be sure to reply and let them know that. We offer suggestions for solving the most obvious causes of the problem first (hear hoofbeats, think horses, not zebras, and all that) -- if those don't solve the problem, then the ticket gets escalated until we find a resolution.  Our staff won't ever knowingly leave you hanging without a resolution!