Failed authorization procedure

Hello, i have problems with certbot. I have read manny forums an they are not helping me. I have a Raspberry 4 4GB RAM

My domain is: scorpioclan.ddns.nez

I ran this command: sudo certbot --apache

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
No names were found in your configuration files. Please enter in your domain
name(s) (comma and/or space separated) (Enter ‘c’ to cancel): scorpioclan.ddns. net
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for scorpioclan.ddns.net
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. scorpioclan.ddns.net (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://scorpioclan.ddns.net/.well-known/acme-challenge/VIHnAen9sGpTqDq3keIdaERsnay45wTYV8mldML-Pxs: Error getting validation data

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: scorpioclan.ddns.net
    Type: connection
    Detail: Fetching
    http://scorpioclan.ddns.net/.well-known/acme-challenge/VIHnAen9sGpTqDq3keIdaERsnay45wTYV8mldML-Pxs:
    Error getting validation data

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

The operating system my web server runs on is (include version): Raspberry Pi OS (32-bit) with desktop

My hosting provider, if applicable, is: noip.com

I can login to a root shell on my machine (yes or no, or I don’t know): yes

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.31.0

Hi @GameBooster

read your check result, ~~40 minutes old - https://check-your-website.server-daten.de/?q=scorpioclan.ddns.net

There is no answer. A working port 80 is required.

Domainname Http-Status redirect Sec. G
http://scorpioclan.ddns.net/ 80.137.56.231 -14 10.026 T
Timeout - The operation has timed out
http://scorpioclan.ddns.net/index.php?page=allow -14 10.043 T
Timeout - The operation has timed out
https://scorpioclan.ddns.net/ 80.137.56.231 -4 0.116 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

Not a timeout. Change that.

1 Like

Hi @JuergenAuer i have istall ufw and port 80 is open to anywhere and i look in iptables and tcp/80 is open1

@JuergenAuer i have see, you live in germany. Können wir bitte deutsch reden?

Your IP address (80.137.56.231) returns an ICMP type 3 (destination unreachable) code 13 (communication administratively filtered) when trying to connect to port 80.

This usually means there is some kind of firewall actively blocking the connection. If it’s not your ufw or iptables, it must be somewhere else.

It could also be your IP address has changed and isn’t 80.137.56.231 any longer and your dynamic DNS needs updating.

Dein Englisch scheint gut genug zu sein :wink:

Irgendetwas blockiert, finde das und entferne es.

PS: Ah, now your port 443 - is a http port and works:

http://scorpioclan.ddns.net:443/index.php?page=allow

So you may have a wrong port forwarding port 443 extern -> port 80 intern.

Port 80 extern -> port 80 intern is required.

1 Like

Ich habe den Fehler gefunden. In meinem Router war der Port 80 nicht offen.

I fund the error. The Port 80 was not open on my Router.

Danke fürs Helfen :wink:

Thanks for help me :wink:

1 Like

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