Challenge failed for domain www.topshelf.website

Help
1

My domain is: www.topshelf.website

I ran this command: sudo certbot certonly

It produced this output: Challenge failed for domain www.topshelf.website
http-01 challenge for www.topshelf.website
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

My web server is (include version): Apache

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

I can login to a root shell on my machine (yes or no, or I don’t know): 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): no

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

2

Hi @JamesMADE

there is a check of your domain ( topshelf.website - Make your website better - DNS, redirects, mixed content, certificates ):

There you see the problem. Only timeouts:

Domainname Http-Status redirect Sec. G
• http://topshelf.website/
95.144.0.143 -14 10.030 T
Timeout - The operation has timed out
• http://www.topshelf.website/
95.144.0.143 -14 10.026 T
Timeout - The operation has timed out
• https://topshelf.website/
95.144.0.143 -14 10.023 T
Timeout - The operation has timed out
• https://www.topshelf.website/
95.144.0.143 -14 10.027 T
Timeout - The operation has timed out
• http://topshelf.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.144.0.143 -14 10.027 T
Timeout - The operation has timed out
Visible Content:
• http://www.topshelf.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.144.0.143 -14 10.027 T
Timeout - The operation has timed out

Your domain isn't visible.

If you want to use http-01 validation, an open port 80 and a running webserver is required.

Is there a running webserver? Or a firewall that blocks? Or a missing router forwarding?

3

I’m using an Apache server which is running.

Theres no firewalls or missing router.

4

Your site doesn't answer. Is it a home server? So your ISP blocks port 80?

If not, there must be a blocking instance. Or it's a wrong configuration (perhaps the wrong port).

5

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