WEB ADMIN PANEL NOT OPENING

[gooindia]

HI.. I AM NEW TO CENTOS.. I AM USING GOOGLE CLOUD CONSOLE AND REGISTERED A DOMAIN WITH GODADDY.. AFTER THAT I INSTALLED WEB PANEL AND SUCCESSFULLY RECEIVED PASSWORD TOO..
BUT WHEN I TRY TO CLICK http://SERVER_IP:2030/ It's NOT OPENING... PLEASE TELL ME WHERE IS THE PROBLEM.
OR IS THERE NEED TO CHANGE ANY IN MY DOMAIN??

[24x7servermanagement]

Try to disable iptables or csf to see if panel is working or not.

# service iptables stop

# csf -x

[gooindia]

tried.. but not able to open.. any other idea?

[24x7servermanagement]

SSH to server and fire this command :-

Code Select Expand

sh /scripts/restart_cwpsrv

[ishanjn05]

I am also facing same problem. I am using CentOS v7.

I also check "iptables" and "Port" -

Port is listening -
   [root@xxxxxxxxxxxxxxxxxxxxx ~]# lsof -i :2030
   COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
   cwpsrv  794 root   24u  IPv4  15146      0t0  TCP *:device2 (LISTEN)
   cwpsrv  796 root   24u  IPv4  15146      0t0  TCP *:device2 (LISTEN)
  cwpsrv  797 root   24u  IPv4  15146      0t0  TCP *:device2 (LISTEN)

----------------------------------------------
iptables configuration -

[root@xxxxxxxxxxxxxxxxxxxxx ~]# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
f2b-SSH    tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:2030
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:2031

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain f2b-SSH (1 references)
target     prot opt source               destination
REJECT     all  --  61.177.172.60        0.0.0.0/0            reject-with icmp-port-unreachable
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Can you please provide some guidance how can i resolve this problem?
Thanks in advance.

[studio4host]

since the port 2030 is a custom port it's probably closed by your server provider and you need to check that with them.