Support & FAQs

Certify the web aims to be easy to use and to get you setup with your TLS/SSL certificates as quickly as possible. Web hosting configurations vary and sometimes securing your site can be harder than expected, but the good news is that thousands of other users have succeeded before you. There are a few things that are good to know should you run into any problems:


App hangs or Message 'Request Failed..'

Assuming your server has direct access to the internet without a proxy (required), you can also Check the status of the Let's Encrypt service

I get the error "Automated checks for extensionless content failed.."

This means your web server configuration is not allowing files with no extension to be served to site visitors. Unfortunately this is a requirement of the Lets Encrypt service in order for it to fetch the verification file which is automatically created within your site when you request a certificate (more info).

To help with this requirement we try to automatically configure this for you. If you look in {your site}\.well-known\acme-challenge you will see we have created a web.config and a file called configcheck. If you can't browse to this configcheck file in your web browser (http://{your site}/.well-known/acme-challenge/configcheck then the Lets Encrypt service can't access the files it needs either. You can edit the web.config file in this folder to get extensionless files working, then you can re-request your certificate. A mimeMap entry for either "." or ".*" usually works depending on your operating system version.

I have multiple different IP bindings on the same IIS server, how do I manage these?

The default setting for bindings is use 'All Unassigned' and enable SNI (Server Name Indication), this is ideal for many sites but if you have websites bound to multiple different IPs on your server you must specify which IP to create bindings against when you add each Managed Site. Each Managed Site can only be mapped to one IP but multiple domains on one site can be managed as several individual Managed Sites. Yes, this is where it starts to get complicated.

My existing wildcard certificate is showing up instead of a Let's Encrypt certificate

Check the existing bindings you have on your sites. If you are binding to a specific (shared) IP address with a wildcard cert as your default fallback for https requests it will take precedence over other bindings on the same server on the same IP address (even if they are using SNI etc).

Get Help

Registered users can create a new support request for help. Email apps {at}, describing the problem in details, including details of the email address you used when registering for a license key.