The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SSL on server root domain

Discussion in 'General Discussion' started by tylerl, Feb 24, 2010.

  1. tylerl

    tylerl Active Member

    Joined:
    Dec 11, 2009
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    I'm sure someone MUST have mentioned this before, because it's got to be a common issue, but search yielded nothing relevant. So here we go:

    My domain name is "example.com" where I resell hosting services. I have a server called "server1.example.com" controlled by cpanel. The IP address mappings are as follows:

    server1.example.com: 192.168.0.1
    example.com: 192.168.0.2
    [default IP address for new domains]: 192.168.2.10

    This mapping is confirmed in the DNS tool and using "dig" from the command line.

    Everything works fine until I try to put an SSL certificate on example.com. Even though example.com is on an IP of it's own, the "show IP address usage" tool incorrectly lists server1.example.com as sharing 192.168.0.2 with example.com, and indeed the SSL certificate installation fails. I check the generated httpd.conf file, and find that server1.example.com is indeed incorrectly attached to 192.168.0.2 -- in direct conflict with the DNS settings.

    Not to be deterred, I move example.com to 192.168.0.3. "Show IP address usage" now lists them on separate IPs, so we should be fine now. I go to install the SSL certificate, and it fails again! What? Why?

    I run /scripts/rebuildhttpdconf and find that against my will, server1.example.com has now MOVED to 192.168.0.3! Refreshing "Show IP Address Usage" now reflects that move; and 192.168.0.2 has been vacated. The DNS records STILL list the name server1.example.com as correctly pointing to 192.168.0.1 -- but apparently WHM is paying no attention to it's own configuration.

    The "solution" that I've heard is to register another domain name: something like example-servers.info, and change the server name to "server1.example-servers.info". That's not a solution. That's a workaround.

    This is crappy.
     
Loading...

Share This Page