My domain is: dev.tierschnack.de I ran this command: The internal ACME client from KeyHelp It produced this output: [17-Jun-2024 15:10:26] INFO | Sending signed request to " https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/12798603533/Uqq7lg ". [17-Jun-2024 15:10:27] ERROR | Apache: a Le…

So, finally, it works. Was a rules problem in my firewall. But still no clue why it worked from some hosts and not from others. But for the moment I'm happy and don't really care why :slight_smile: The thx goes to Florian from the KeyHelp support forum.

[image] MikeMcQ: TLS-ALPN challenge I must admit, I'm not so deep into LE to know details, they make a good job, it just works. So this is the first time I have issues, so I need to take a deeper look. I suppose it is HTTP01 challenge what I use. Just installed certbot and that python stuff…

[image] 24unix: I don't want to bother the DNS admin to update the pointers just because I change my setup. You may have to bother them if you can't figure out why Let's Debug and Let's Encrypt time out using that domain with that IPv6 address.

Unlike ipv4 ipv6 doesn't do NAT so DDNS running on router is invalid for server behind the router: you'd need to run DDNS on that server itself btw dev subdomain doesn't have ipv4 and just a ipv6: is that expected?

[image] orangepizza: ipv6 doesn't do NAT I've been able to NAT IPv6

@MikeMcQ That's what I'm trying to do. Currently it seems to be a issue on the AWS side, as I can reach port 80 from outside. And someone else from the KeyHelp forum, too.

It's not specific to AWS, connecting to your site doesn't work from my home connection either (in the northeast United States, and yes I'm using IPv6).

[image] 24unix: Currently it seems to be a issue on the AWS side Which AWS "side"? All of them? Let's Encrypt uses four different AWS regions across the world. I think my own test server is even in a different one from those. Further, the primary LE auth center is not in AWS and that can'…

Looks like you resolved some of your connection problem. I can now reach your domain using HTTPS (port 443). Just port 80 is failing. curl -i -m8 http://dev.tierschnack.de curl: (28) Connection timed out after 8000 milliseconds curl -ik -m8 https://dev.tierschnack.de HTTP/2 302 location: http:/…

OK, some other users from Germany can reach both ports, some not. I has to adapt the IP, but that's not related to the LE issue. A user made a test from a VPN in Amsterdam: nmap -6 dev.tierschnack.de Starting Nmap 7.80 ( https://nmap.org ) at 2024-06-17 20:46 CEST Nmap scan report for dev.tiers…

Yes, comms problems like that can be very difficult to debug and resolve. I think you are now convinced this is not related to Let's Encrypt. I am not sure this will help you but sometimes a traceroute helps identify where to look or who best to contact. You may need to involve your ISP or other …

Timeout receving the certificate

Help

Topic		Replies	Views
Connection timeout Help	37	22170	June 27, 2017
Problèmes de connexions : Aide (en français)	17	1027	February 4, 2023
Issuing Certificate Failed due to timeout, but domain/port are reachable Help	38	1203	August 28, 2023
Timeout during connect (likely firewall problem) Apache2 Ubunut 20.04 server, updated info Help	6	763	September 2, 2020
Possible IP blocklist? Help	53	2482	August 5, 2022

Timeout receving the certificate

Related topics