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 secr…

all thanks, the problem was solved. On our node equipment was exposed mtu 1496. Somewhere on the road there was no support for fragmentation, probably in my side.

[image] alabor: I ran this command: curl https://acme-v01.api.letsencrypt.org/directory It produced this output: curl: (35) TCP connection reset by peer Is this still ongoing and consistent? Please show the IP resolved for acme-v01.api.letsencrypt.org . It seems to be working fine from wh…

It could be related to [image] OSCP servers are inaccesible from some servers Issuance Tech I… if the ACME endpoint also shares an IP address on Akamai with a service that the Russian government is trying to block Internet users from accessing. (This is a different s…

curl_8025021512.pcapng (6.2 KB) [root@web ~]# traceroute acme-v01.api.letsencrypt.org traceroute to acme-v01.api.letsencrypt.org (2.23.157.115), 30 hops max, 60 byte packets 1 80.250.215.61 (80.250.215.61) 0.187 ms 0.263 ms 0.217 ms 2 10.129.0.15 (10.129.0.15) 1.097 ms 1.008 ms 1.193 ms …

[image] alabor: 5 mskn06.msk112.transtelecom.net (217.150.45.178) 3.085 ms 3.113 ms 3.198 ms There is another thread which had problems with transtelecom: OSCP servers are inaccesible from some servers - #14 by schoen

[image] alabor: acme-v01.api.letsencrypt.org Note that the IP addresses that I offered in the other thread were for ocsp.int-x3.letsencrypt.org rather than acme-v01.api.letsencrypt.org, although both are hosted by Akamai. (CDN IP addresses intended for use with one hosted service won't necess…

[root@web ~]# traceroute acme-v01.api.letsencrypt.org traceroute to acme-v01.api.letsencrypt.org (23.77.91.5), 30 hops max, 60 byte packets 1 80.250.215.61 (80.250.215.61) 0.209 ms 0.192 ms 0.240 ms 2 10.129.0.15 (10.129.0.15) 1.013 ms 1.087 ms 1.188 ms 3 176.74.8.80 (176.74.8.80) 2.23…

ocsp.int-x3.letsencrypt.org works without problems [root@web ~]# curl -v -4 ocsp.int-x3.letsencrypt.org About to connect() to ocsp.int-x3.letsencrypt.org port 80 (#0) Trying 188.43.76.81... Connected to ocsp.int-x3.letsencrypt.org (188.43.76.81) port 80 (#0) GET / HTTP/1.1 User-Agent: curl/7.2…

but if I change the ip-address on the same machine from another subnet everything works fine. The route is the same. (see the attachment) changeIP.txt (4.1 KB) what’s the problem? please help…

It seems that one subnet is blocked from accessing 23.77.91.5:443 while the other is not. This does not appear to be a certificate issue nor a renewal configuration issue. It seems more like a firewall/network related issue - either at your end or somewhere along the path; hard to say and even har…

[solved] Probably my addresses was banned

Help

bytecamp October 30, 2017, 3:50pm 5

There is another thread which had problems with transtelecom: OSCP servers are inaccesible from some servers - #14 by schoen

Topic		Replies	Views
My ip is blocked? Help	12	870	June 25, 2023
Unable to connect to ACME server Help	28	1528	June 21, 2024
Can't connect to acme-v02.api.letsencrypt.org Help	49	20244	February 7, 2022
IP from webserver blocked? Help	14	328	October 16, 2024
"Connection reset by peer" Help	24	4912	May 22, 2020

[solved] Probably my addresses was banned

Related topics