Troubleshooting with SSL

If your SSL certificate is not issued, or if you have problems when renewing it, please check the following.

Could you wait 24-72 hours after adding the domain and changing the nameservers?

If you have just created an account or added a domain, it may take up to 24 - 72 hours for the SSL settings to be reflected, so please be patient.

Are there any mistakes in the nameserver settings?

Are there any mistakes in the nameserver settings?

Please check How to add a new domain to make sure there are no mistakes in the settings.

Is there any unnecessary description in the ".htaccess" file of the document root?

When you move from another company's server to mixhost, etc., the .htaccess file of the document root may contain the PHP version setting description etc. on the other company's server.
Mixhost may have problems using SSL if it contains unnecessary descriptions.

In particular, problems often occur with .htaccess files that contain FastCGI-related content, such as:

AddHandler fcgid-script .php .phps
FCGIWrapper "/home/example/".php
FCGIWrapper "/home/example/".phps

If you cannot use SSL, please try to change the minimum .htaccess file first.

Do you have Basic Authentication set in your document root?

You must be able to access mixhost using your domain name.
If password restrictions, etc., are set by basic authentication, access will not be possible, and an SSL certificate will not be issued.

Regarding basic authentication, please use it within the subdirectory.

Are you restricting access to the document root by IP address?

An SSL certificate cannot be issued if access is restricted by IP address.
Regarding access restrictions, please use only within the subdirectory.

Do domain names and subdomains exceed 64 characters?

Cannot be used for domain and subdomain names longer than 64 characters.

Does the document root directory exist?

Please be sure to create the document root directory.

Does your domain name contain strings from the banned countries list?

mixhost uses Sectigo (COMODO) SSL certificate.
We refuse to issue an SSL certificate if the domain name contains a character string from a specific prohibited country list or if the domain is prohibited by the company.

In this case, SSL cannot be used.

Is my Safe Browsing status safe?

For sites that are not safe with Google Safe Browsing, we cannot issue an SSL certificate.

Are the URLs beginning with "http://" and "https://" mixed together?

If you get a warning on your browser, it may be because the content (videos, CSS, etc.) on the site contains content that starts with "http://". Please use "https://" for all content.

No similarities to existing major domains?

Sectigo (COMODO) may refuse to issue an SSL certificate if it contains the same character string as a famous web service that already exists, or if it is similar.

SSL cannot be used in this case.

Have you enabled the CDN's security features?

If you are using a CDN such as Cloudflare, the CDN's own security function may block access from Sectigo (COMODO), which is the issuer of the certificate, causing a phenomenon where the certificate cannot be issued. I have.

Please check if the following IP addresses are blocked, and if so, please unblock them.

Sectigo IP

After troubleshooting

If the error continues, please contact support.
In addition, we would appreciate it if you could check the failure information of mixhost and the failure information of Sectigo, which is the issuer of the certificate.



Was this article helpful?
0 out of 4 found this helpful