[SOLVED] Certbot - Confusion About How To Deal with A Certificate Which Doesn't Cover the Right Domain Names

For experimentation or testing, you can use --staging, which uses a test CA instead of the real CA.

The limit that you hit will clear after 1 hour (so it should already have cleared up a while ago).

1 Like

In desperation I reverted to a two week old backup and replaced all the https references. Johns-Jokes now loads on FireFox but still problems on many other browsers :frowning:

Once again I tried every option and still unable to get the site working in HTTPS.

I am open to suggestions as to the correct and exact commands and parameters to use.

Delighted to say I managed to install the certificate :slight_smile:

I have four other working certificates and…

  1. deleted existing problematic LetsEncrypt settings

  2. replicated the DigitalOcean’s Networking A and CNAME records

  3. replicated the working configurations in /etc/apche2/sites-avalable/

sudo certbot displayed every URL and selecting the problematic URLs worked like a charm.

Many thanks for all the helpful suggestions.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.