Skip to main content
We are aware of an issue after updating to cPanel versions 11.110.0.65, 11.126.0.21, or 11.128.0.11, some cPanel plugins or features are no longer functioning properly including WP Toolkit. Please see the following article for more information and updates:
Update to latest cPanel 110, 126, or 128 versions removes "addonfeatures" directory.

No SSL for WHM

Comments

11 comments

  • SimpleSonic
    Can you be more specific?
    0
  • cPRex Jurassic Moderator
    There shouldn't be any clicking required to get the free hostname SSL that cPanel provides, so I am also not sure what you mean by "one-click installation." If you have any additional details to provide that would be helpful, but showing us the output from /usr/local/cpanel/bin/checkallsslcerts (with any domains or IP addresses obfuscated for security) may be helpful as well.
    0
  • Networkologist
    Hosting with Linode and it may have something to do with my not knowing how to setup a proper reverse dns. Currently its: 69-164-199-193.ip.linodeusercontent.com I ran: /usr/local/cpanel/bin/checkallsslcerts and get: cpcalendars.secure.highdesertdigital.net: Attempting HTTP DCV preflight check "?" "??cpcalendars.secure.highdesertdigital.net"? does not resolve to any IP addresses on the internet. www.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??www.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. whm.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??whm.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. mail.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??mail.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. cpanel.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??cpanel.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. webmail.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??webmail.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. cpcontacts.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??cpcontacts.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet. cpcalendars.69-164-199-193.ip.linodeusercontent.com: Attempting HTTP DCV preflight check "?" "??cpcalendars.69-164-199-193.ip.linodeusercontent.com"? does not resolve to any IP addresses on the internet.
    0
  • cPRex Jurassic Moderator
    You'd need to change the system to a real hostname. The automatically-generated one from Linode isn't something you would be able to secure. I'd configure the hostname, then give the system 24 hours or so for the DNS to propagate, and then I would expect the SSL to be installed automatically by cPanel.
    0
  • Networkologist
    You'd need to change the system to a real hostname. The automatically-generated one from Linode isn't something you would be able to secure. I'd configure the hostname, then give the system 24 hours or so for the DNS to propagate, and then I would expect the SSL to be installed automatically by cPanel.

    I Set up the hostname in WHM. I don't know what to change in Linodes "Manager" Or the ssh command to change it.
    0
  • cPRex Jurassic Moderator
    Can you try using our guide here? Change Hostname | cPanel & WHM Documentation
    0
  • Networkologist
    From ssh: [root@secure ~]# hostname REDACTED [root@secure ~]#
    0
  • cPRex Jurassic Moderator
    That's a good sign. Ensuring that it was done through the WHM interface will make sure all the correct places on the server are updated, which seems like it wasn't the case since the checkallsslcerts command is showing the old default hostname. Can you try updating that again using the WHM tools? I also see the hostname is responding in DNS to a 172.64.x.x IP address, so it seems all is well in the DNS configuration.
    0
  • Networkologist
    That's a good sign. Ensuring that it was done through the WHM interface will make sure all the correct places on the server are updated, which seems like it wasn't the case since the checkallsslcerts command is showing the old default hostname. Can you try updating that again using the WHM tools? I also see the hostname is responding in DNS to a 172.64.x.x IP address, so it seems all is well in the DNS configuration.

    Same. I'll try putting a ticket in to linode and post back.
    0
  • Networkologist
    err... So my hostname was Proxied @ cloudflare so the CF IP was denied. When I "unchecked" the Proxy setting i.e. so it wasn't orange, Voila! Site is now SSL.
    0
  • cPRex Jurassic Moderator
    Nice catch!
    0

Please sign in to leave a comment.