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. crt.sh | example.com ), so withholding your domain name here does not increase secrecy, but …

what can it be if it's not a firewall ?

root@localhost:~# zgrep Ban /var/log/fail2ban.log* |grep http root@localhost:~# i have nothing else

By the way i dont know why cert would be banned

Are you sure your webserver is running? --standalone not complaining about the port being occupied is a little suspect.

if standalone works obviously its not a firewall or whatever else issue

But standalone no longer works.

I don't understand why you keep saying they work, when the LE logs show a connection problem: [image] tlloancy: Detail: 172.105.247.238: Fetching https://www.benedicte-pavageau.com/.well-known/acme-challenge/VMUrmvkm0L-ch0jJ-piVS7m1Ocry8UhMOPKPymxBLFU: Timeout during connect (likely firewall …

Webroot renewal timeout - works on standalone only

Help

MikeMcQ October 3, 2023, 6:25pm 41

Yeah @9peppe the symptoms are odd. They are also doing two threads with similar problems but different domain names

See especially

Topic		Replies	Views
Failing to renew via either apache or webroot Help	9	2736	August 2, 2017
[Solved] Webroot Renewal Fails Help	27	5761	November 1, 2017
Can't update certificate, get weird error Help	18	1179	September 26, 2021
Certbot renew not working Help	15	2215	November 23, 2018
Certbot unable to renew: Invalid response Help	25	1395	March 22, 2023

Webroot renewal timeout - works on standalone only

Related topics