Same problem here, but it isn't the firewall
I'm a linux n00b and thought I'd try unmanaged VPS with CentOS to see how far I'd get never having written a line of shell command before in my life.
After restoring an image provided by the hoster, my DirectAdmin can't be reached on port 2222 either. Though if I pull up the IP of my server in my browser, I get the "Apache is functioning normally" message. This leaves me to believe my only problem is with DirectAdmin
So this is what I did:
[logged on as root]
service iptables stop
I go to: myservip:2222.
Still the same problem.
service iptables start
In other words, for me it's not the firewall. I decided to check firewall rules further just in case...
rpm –q iptables
Iptabels version -1.3.5-5.3.e15_4.1
lsmod | grep ip_tables
NO RESPONSE, just black.
Iptables –L
Chain Input (Policy accept)
target prot opt source destination
Chain forward (policy accept)
target prot opt source destination
Chain output (policy accept)
target prot opt source destination
It would be a correct conclusion my firewall rules are EMPTY, right?
lsmod | grep ip_tables didn't even tell me which state the firewall is in. Is it a correct conclusion that if you don't have any rules in your firewall it gives no response to this command?
I also cannot start or stop directadmin, nor can I view directadmin's error log since it gives me a 'permission denied' error.
If anyone out there has some answers for me, I'd really appreciate it. Dying to learn this. Thank you.