Skip to main content

AutoSSL displays wrong Certificate

Comments

12 comments

  • Peoplespaces
    Just an update. It appears the first alphabetical domain name account on the shared IP is made the primary account and SNI not required. Deleting the SSL host makes the next alphabetical account the primary account.
    0
  • cPanelLauren
    Just an update. It appears the first alphabetical domain name account on the shared IP is made the primary account and SNI not required. Deleting the SSL host makes the next alphabetical account the primary account.

    This is Apache's normal behavior when you're attempting to view a site over https without an https VirtualHost. If the sites you're attempting to view do in fact have certificates something is woefully wrong. Can you also confirm that the https VirtualHost for the domains was created?
    0
  • Peoplespaces
    This is Apache's normal behavior when you're attempting to view a site over https without an https VirtualHost. If the sites you're attempting to view do in fact have certificates something is woefully wrong. Can you also confirm that the https VirtualHost for the domains was created?

    Sorry to sound dense but how would I determine that the Virtualhost was created?
    0
  • cPanelLauren
    Hi @Peoplespaces I apologize for not providing the instructions. An https VirtualHost is created within the Apache configuration at /etc/apache2/conf/httpd.conf
    and will look something like the following in the first line:
    0
  • Peoplespaces
    Server does not have that file. Would it be different with Cloudlinux?
    0
  • cPanelLauren
    It shouldn't be different with CloudLinux are you running EasyApache 3 or EasyApache 4? Thanks!
    0
  • Peoplespaces
    EAsyApache 3.
    0
  • cPanelLauren
    Hi @Peoplespaces In that case the apache configuration file should be at: /usr/local/apache/conf/httpd.conf
    0
  • Peoplespaces
    OK. The sites in question have the Virtualhost IPADDRESS:80 there but not the 443 In fact they seem to be stuck in the pending AutoSSL queue for more than a week.
    0
  • cPanelLauren
    Hi @Peoplespaces At this point, it might make it easier if you could please open a ticket using the link in my signature. Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • Peoplespaces
    Ticket ID 10453021
    0
  • cPanelLauren
    Hi @Peoplespaces I checked in on your ticket this morning and it appears the analysts found that you were blocking ip's beginning with 91. in the .htaccess for the domains that didn't get certificates. Because this will cause DCV checks to fail the solution was to remove the IP address. Once this was completed the domains were able to have the DCV checks completed successfully. Are you still experiencing any further issues? Thanks!
    0

Please sign in to leave a comment.