Problems and solutions of HTTPS error sorting in micro-_javascript program

Common problems and solutions for HTTPS error of micro-mail program

Micro-credit Procedures Open public test has been one months, because the official requirements of the document requires the background to use HTTPS request for network communication, the domain name and the protocol does not meet the requirements can not be requested. More and more developers are using SSL certificates to practice the application of micro-trust programs, but still encounter various problems. This article lists the common errors and solutions for SSL certificates for developers ' reference.

FAQ One

In the process of the micro-letter applet, almost every developer in the process of practice encountered the following error:

Reasons and Solutions:

This is because Wx.request initiated the HTTPS request, the micro-letter applet read most of the request API interface, must have an HTTPS protocol to use, or will prompt the domain name is not legal. This means that the micro-mail applet is a mandatory use of SSL certificates, otherwise it will not run.

FAQ Two

"You cannot verify this certificate to a trusted certification authority" or something like "The security certificate is issued by a company that you do not have a selected trust".

Reasons and Solutions:

This problem may occur because the SSL certificate top-level root is not in the browser's trust list, or the SSL certificate was issued by an untrusted organization. You can effectively resolve this issue by selecting a certificate authority that the browser trusts to request an SSL certificate.

FAQ Three

Visit the site to see the certificate is not the one I installed.

Reasons and Solutions:

This may be caused by the same IP on the server and multiple certificates installed on the port. The SSL protocol allows only a single certificate to be returned on one IP port. You can solve this problem by assigning different port numbers or different IP addresses.

FAQ Four

The Web site certificate has expired or has not yet taken effect.

Reasons and Solutions:
in this case, you can view the certificate information as the valid start and end dates identified in the red box below to determine whether the certificate is within the validity period. If within the validity period, need to check the computer date is correct, if not within the validity period, need to contact your customer service personnel to reapply as soon as possible.

FAQ Five

Whether the domain name of the Web site is inconsistent with the domain name in the certificate

Reasons and Solutions:

This may be because the domain name of the background server is inconsistent with the domain name that is bound in the installed SSL certificate. Which domain names need to use HTTPS connection, you must bind the domain name to the certificate for verification. If you are involved in multiple domain names or multiple level two domain names, you can use a multiple domain name certificate or wildcard certificate to implement a certificate binding multiple domain names.

FAQ Six

HTTPS request failed

Reasons and Solutions:

The micro-letter requires that the TLS protocol for the backend server be TLS1.2 and above, and if the HTTPS request fails, check to see if the server's TLS version meets the requirements.

Thank you for reading, I hope to help you, thank you for your support for this site!