Having an error with letsencrypt, saying the site has a certificate, but it does not and I cannot get one

My domain is: millenniumairship.com

It is hosted on angryhosting.com, who has the free letsencrypt service on it, but is not listed in your hosting provider list. I moved the hosting from Network Solutions to Angryhosting this month, with a brend new site installation. But somehow it thinks it already has a certificate and won't let me generate a new one. Not only is the folder it references non-existent in the new site, but I had also downloaded the entire old site from Network Solutions as a backup and that folder is not in there, either. So I can't just FTP that directory into the new site. This is the error I get on the angryhosting control panel:

Sorry, here is the error:

Hello @cvettersdesign, welcome to the Let's Encrypt community. :slightly_smiling_face:

Did you click the "Retrieve Certificate" button? I am assuming you did.

Here is what I see:

From here: SSL Server Test: millenniumairship.com (Powered by Qualys SSL Labs)

$ curl -k -Ii https://millenniumairship.com
HTTP/2 301
server: nginx
date: Sun, 15 Nov 2026 18:47:33 GMT
content-type: text/html
content-length: 162
location: https://www.angryhosting.com/

$ curl -k -Ii https://www.millenniumairship.com
HTTP/2 301
server: nginx
date: Sun, 15 Nov 2026 18:48:16 GMT
content-type: text/html
content-length: 162
location: https://www.angryhosting.com/

$ curl -k -Ii  https://www.angryhosting.com/
HTTP/2 200
server: nginx
content-type: text/html; charset=UTF-8
cache-control: no-cache, private
date: Sun, 15 Nov 2026 18:47:47 GMT
set-cookie: XSRF-TOKEN=eyJpdiI6ImkxTkt5RXE2VGZWbmdudzBERGphTWc9PSIsInZhbHVlIjoickd6WllHcm1YZmh1N095czBBcHpkNDdUKzNhWjJDYXpOc1lnV0txbkoybVVVdTUwa0NaaFwvc2JLUlBvMVV5V3MiLCJtYWMiOiJhMWY4Zjg1NjQ5MjU4YzkzNDIxMjMyNTcwMGMwMDk0YmQwOGY0MGNlMDJiZDRhNWViOGYzODU4OTBjNDJjYWRhIn0%3D; expires=Sun, 15-Nov-2026 20:47:47 GMT; Max-Age=7200; path=/
set-cookie: angryhosting_session=eyJpdiI6IjUwU3kwSG5LbG9HaVN4K012cFp3VkE9PSIsInZhbHVlIjoieGdmZEw1NnRXRWdIMXR1NTI5empTdnc2VEtaN09cL1NvZFVIb1RsVUZPN3VCUmZHTVhBTHJGQklTeGhWdEJacm8iLCJtYWMiOiJlOTljYTE0OTQwOTdjNmVkMjdkZDJjMmRiMGZjYmQwNzJkMzgwNzIzYWY0ZmQwMzIzOTRjZWNiMjcwMzdmNDA4In0%3D; expires=Sun, 15-Nov-2026 20:47:47 GMT; Max-Age=7200; path=/; httponly

Additional supplemental details.

Ports 80 & 443 are open.

$ nmap -Pn -p80,443 millenniumairship.com
Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-11-15 18:46 UTC
Nmap scan report for millenniumairship.com (68.94.116.145)
Host is up (0.040s latency).

PORT    STATE SERVICE
80/tcp  open  http
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 0.29 seconds

For the redirection:

$ nmap -Pn -p80,443 www.millenniumairship.com
Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-11-15 18:46 UTC
Nmap scan report for www.millenniumairship.com (68.94.116.145)
Host is up (0.050s latency).

PORT    STATE SERVICE
80/tcp  open  http
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
$ curl -Ii http://millenniumairship.com
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 15 Nov 2026 18:44:53 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Redirect-By: WordPress
Location: http://www.millenniumairship.com/

And it redirects to here:

$ curl -Ii http://www.millenniumairship.com/
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 15 Nov 2026 18:45:07 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Link: <http://www.millenniumairship.com/wp-json/>; rel="https://api.w.org/"
Link: <http://www.millenniumairship.com/wp-json/wp/v2/pages/9>; rel="alternate"; title="JSON"; type="application/json"
Link: <http://www.millenniumairship.com/>; rel=shortlink

When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: millenniumairship.com

I ran this command:

It produced this output:

My web server is (include version): server: nginx

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: angryhosting.com

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Thank you for assisting us in helping YOU!

image

Something doesn't add up...

And from this page: AngryHosting - Affordable Domain Hosting

I find this "This feature is currently in beta, though we have been using it for a short while and feel comfortable with its performance and reliability. Please contact us if you have any issues or requests for additional features!"

I don't find that this is always up-to-date to this moment but here is a list of previously issued certificates crt.sh | millenniumairship.com

If you know what this mean, please share the output of this command.

  • sudo nginx -T that is a capital T

On the bottom of that page: Posted on April 9th, 2017

So, probably not in beta anymore :slight_smile: Good idea to have them contact the hosting company tech support though. @cvettersdesign The hosting company's tech support can likely resolve this pretty quickly. They have the best insights on how their system works.

As an aside, the cert history Bruce showed is all for wildcard certs. But, from the new hosting company's instructions I don't believe they will get a wildcard cert as they'll use an HTTP Challenge. Which is fine but I think those certs were from their old system.

Just their documentation still in beta. :laughing:

I did click on the button, but it just returned an error. However, my friend from Angryhosting got it to work on the back end this afternoon. So now it’s working fine. Thanks!

Christopher Vetters Design

Glad it is working for now @cvettersdesign :slight_smile:
Have pleasant day. :sun:

I know, that was what was bugging me. The site had been https until I moved it from from Network Solutions, but the error was telling me that the certificate would run out in 2014. 12 years ag. So it was working but this was obviously another issue. And all of it was keeping me from retrieving a proper certificate for the new hosting service.