Resolving HTTPS setting - ArvanCloud

ArvanCloud Blog

Read more about ArvanCloud news,
updates, products and services in ArvanCloud weblog.

Resolving HTTPS setting

2 Jul 2019

One of the most important concerns about critical websites, is showing the content correctly through a safe web protocol (HTTPS). In this article we will try to describe the most important issues that could cause anomalies in a website while using HTTPS.

Primary HTTPS Setting

Here you can learn about resolving HTTPS settings.

If you want your website to be accessible through HTTPS protocol, you need to upload your certificate including a private key file and a public certificate on your ArvanCloud panel.

Consider the fact that the submitted file formats should match the PEM standard (for more information about PEM click here.

And we emphasize the file certificates should include the root certificates and should be uploaded in a Trust Chain form in ArvanCloud Panel. (Click Here )

You can also use SSL/TLS Certificate for free when using ArvanCloud services. In this situation there’s no need for changing any settings. To learn more about receiving SSL/TLS Certificate you can read the article.

Website Upload Failure through HTTPS

If your SSL/TLS Certificate is not uploaded in ArvanCloud panel, or for any reason the uploaded file includes an error, the HTT{S feature will not be activated in your panel. In this condition, your website won’t be accessible through HTTPS using port 443.  To solve this issue you should upload the correct files with PEM formant.

Using different certificates for different Subdomains

Each certificate is valid for 1 or several domain names. If you are using different certificates for your different subdomains, you need to have a separate panel for each subdomain and upload the related films to that subdomain in the related panel.

Certificate Warning Message for Main Domain

If your certificate is acquired in a wildcard format (for example *.arvancloud.com) , it means all the sub domains can use this certificate, but the main domain itself does not have this permission.

For example, x.arvancloud.com is a valid name, but arvancloud.com and x.z.arvancloud.com are not valid for this certificated. Bear in mind that in most cases the main domain name is defined in the certificate as alternative names, in order to prevent such problems.

Certificate Warning Message on mobile and some devices

It is possible that disregarding the changes in the above mentioned settings, you encounter NET:ERR_CERT_AUTHORITY_INVALID or Your connection is not private message in some browsers, devices or specially mobile browsers. Usually this problem occurs when you have uploaded your certificate file without the public key root or intermediate ca or “without chain”.

To solve this issue and for more information about creating a trust chain you can click here.

We hope this article was useful. If you enjoyed reading it, fee free to share it with your friends.

دیدگاه شما