Timeout during connect

My domain is: atlas-disc.loca.lt

I ran this command: certbot certonly --webroot

It produced this output:
Waiting for verification...
←[31mChallenge failed for domain atlas-disc.loca.it←[0m
http-01 challenge for atlas-disc.loca.it
Cleaning up challenges
←[31mSome challenges have failed.←[0m
←[0m - The following errors were reported by the server:

Domain: atlas-disc.loca.it
Type: connection
Detail: Fetching
Timeout during connect (likely firewall problem)

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version):*

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

My hosting provider, if applicable, is:*

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):*

*: I'm on Windows 10, I'm using MAMP to host and LocalTunnel to portforward. I check with https://check-your-website.server-daten.de/?q=atlas-disc.loca.lt and I didn't find any problem.

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

Hi @Tech_T

if "check-your-website" is able to check your http + port 80 + /.well-known/acme-challenge/random-filename, but Letsencrypt has a timeout, you have something that blocks.

And that

Friendly Reminder

This website is served via a localtunnel. This is just a reminder to always check the website address you're giving personal, financial, or login details to is actually the real/official website.

Phishing pages often look similar to pages of known banks, social networks, email portals or other trusted institutions in order to acquire personal information such as usernames, passwords or credit card details.

Please proceed with caution.
If you're the developer...

You and other visitors will only see this page from a standard web browser once per IP every 7 days.

Webhook, IPN, and other non-browser requests "should" be directly tunnelled to your localhost. If your webhook/ipn provider happens to send requests using a real browser user-agent header, those requests will unfortunately also be blocked / be forced to see this tunnel reminder page. FYI, this page returns a 401 HTTP Status.
Options to bypass this page:

    Set and send a Bypass-Tunnel-Reminder request header (its value can be anything).
    or, Set and send a custom / non-standard browser User-Agent request header. 

This localtunnel session is sponsored by: Tunez.com - music discovery made easy

looks bad. Not a timeout, but not the content "check-your-website" has seen.

Check your firewall / other blocking components. And remove that tool if the path starts with /.well-known/acme-challenge.

Ok, I'll let you know soon.

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