[Rawhead]

Okey, did ask before and all I hear is having all my port open, as they all where.
So I didn't feel I did get enough help when I even said that all my port was set.
(Rented dedicated server box, all services is running from the same box)

Now that I have the debug script I manage to find out a little more about the problem in testing.

SourceBans web console issue, can't connect.

This is the draft for the web test:

[+] SourceBans "Error Connecting()" Debug starting for server XXX:27021

[+] Trying to establish UDP connection
[+] UDP connection successfull!
[+] Trying to write to the socket
[+] Successfully requested server info. (That doesn't mean anything on an UDP stream.) Reading...
[+] Got an response! Server: XXX

[+] Trying to establish TCP connection
[-] Error connecting #13: Permission denied

as you can see web having trouble connecting.

Tried it also through SSH:

[root@XXX test]# php sb_debug_connection.php
[+] SourceBans "Error Connecting()" Debug starting for server XXX:27021<br /><br />[+] Trying to establish UDP connection<br />[+] UDP connection successfull!<br />[+] Trying to write to the socket<br />[+] Successfully requested server info. (That doesn't mean anything on an UDP stream.) Reading...<br />[+] Got an response! Server: XXX <br /><br />[+] Trying to establish TCP connection<br />[+] TCP connection successfull!<br />[+] Trying to write to TCP socket and authenticate via rcon<br />[+] Successfully sent authentication request. Reading...<br />[+] Got an response! <br />[+] Password correct!

Now "[-] Error connecting #13: Permission denied" is indicating a file permission problem, but where can it be? (Where between SourceBans web installation and Server path is this issue)

Funny enough WEB can't connect with all ports open and SSH shell is able to reach it.
Wondering if this can be a SELinux problem in my CentOS 6.5 installation.

Any thoughts?

[Rawhead]

Okey did "setenforce 0" in SSH to disable SELinux temporarily and the readout is complete from web.

[+] SourceBans "Error Connecting()" Debug starting for server XXX:27021

[+] Trying to establish UDP connection
[+] UDP connection successfull!
[+] Trying to write to the socket
[+] Successfully requested server info. (That doesn't mean anything on an UDP stream.) Reading...
[+] Got an response! Server: XXX

[+] Trying to establish TCP connection
[+] TCP connection successfull!
[+] Trying to write to TCP socket and authenticate via rcon
[+] Successfully sent authentication request. Reading...
[+] Got an response!
[+] Password correct!

Now how can I set SELinux to allow this permission without disabling it totally?
Probably not the right forums, but I hope some out there with a little more understanding then me can help me fix this issue.

Just providing more information for a faster troubleshoot.

As I mentioned earlier all the ports was set to in TCP and UDP. I want to thank them for providing an answer, but when I tell them that they are open and do not believe it, then it is hard to troubleshoot it further and get the right help I need.

Thanks in advance.

[Rawhead]

Okey folks. I manage to fix this issue.

Additional thanks to Peace-Maker for the debug script and putting me into the right direction. You are a life saver. And quick to respond.
Continue to do what you do. Maybe I see you again in these forums.

[Rawhead]

I'm not doing this to advertise my gaming community, but to provide a full guide to this very same problem. I do not have anything to do with the SourceBans team nor an author of Sourcebans.

I just want to help people in a similar position.
My web address to this guide: http://fragsgaming.com/forum/viewtopic.php?f=13&t=61

Please respect my work, and do not copy it without my express permission.
I will allow Alliedmods.net SourceBans team to use this if they like for a possible troubleshooting and or FAQ guide in the future if they so wish to, if so please keep it copyrighted by us..

[Peace-Maker]

Nice to see you fixed it! Thanks for sharing.