Primary Domain gives "connection refused"

propopulus

• January 05, 2015 20:51

Hello, I recently installed a CloudLinux WHM/Cpanel dedicated server in a business. It is behind a router (with Static IP), port 80 is forwarded to the dedicated server, along with 2087,2083. The fully qualified hostname works. "server.example.com:2087" However, the domain name "example.com" is not working. It gives a "connection refused" error. I have setup a cpanel account and it should be working. Does anyone know what I should do now? -Thanks

• 

  kiraanmore

  • January 06, 2015 05:17

  Re: Help: Primary Domain gives "connection refused" Hello, You should check below things. 1. If httpd service is running on your server. You can check this using below command : /etc/init.d/httpd status 2. Check if port 80 is open on the server. Try to stop iptables and check your website. To stop iptables use below command : service iptables stop If your website starts working, you would need to open port 80.

  0
• 

  anton_latvia

  • January 06, 2015 09:13

  Re: Help: Primary Domain gives "connection refused" What is main IP for the server? I see obvious configuration conflict here. Because your server is LAN-hosted - it must have local IP - and local IP is assigned to virtual host aswell (you can see it in "List accounts"). But in DNS domain must have public IP and therefore when you access example.com with public-ip - apache, that is configured with local-ip can not find it. When you access WHM - server does not check for IP - basically it answers on a port, but apache does more IP/domain mapping.. It won't work without some workaround, manual I suppose.

  0
• 

  cPanelMichael

  • January 06, 2015 17:45

  Hello :) Please also review the following document if you prefer to use a NAT environment: 1:1 NAT Thank you.

  0
• 

  propopulus

  • January 07, 2015 09:06

  Thanks for all your help, it turned out to be I needed to forward the UDP DNS port. That fixed it.

  0
• 

  cPanelMichael

  • January 07, 2015 16:30

  I am happy to see you were able to address the issue. Thank you for updating us with the outcome.

  0

Please sign in to leave a comment.