Certbot error on generate subdomain why?

i use this command and if use only -d www.smartit.it -d smartit.it all its ok certificate generate

sudo docker run -it --rm --name certbot -v /var/www/html:/var/www/html -v "/etc/letsencrypt:/etc/letsencrypt" -v "/var/lib/letsencrypt:/var/lib/letsencrypt" certbot/certbot certonly -d www.smartit.it -d smartit.it -d testjenkins.smartit.it --webroot --webroot-path /var/www/html --expand

but if add subdomain testjenkins.smartit.it receive this error

The following errors were reported by the server:

Domain: testjenkins.smartit.it
Type: unauthorized
Detail: Invalid response from
https://testjenkins.smartit.it/.well-known/acme-challenge/4rrZq8v6t9Y_tj8XGtuvH_jQmUbCkmLRbLQcZnjUZdk
[54.74.176.126]: "\n\n503 Service
Unavailable\n\n

Service"

but if ping a receive same ip

i Ping testjenkins.smartit.it [54.74.176.126] con 32 byte di dati:

The webserver configuration for testjenkins.smartit.it is most likely flawed. It's not limited to the ACME challenge, but https://testjenkins.smartit.it/ is giving a 503 Service Unavailable error too. Is it a reverse proxy by any chance? If I look at the response headers for your main site, I'm seeing headers like X-ServerName: ipvsproxy182.ad.aruba.it which has a totally different IP address than the 54.74.176.126 of your hostnames.

Hi @nturri1306

Certbot error on generate subdomain why?

Why? Your configuration is terrible buggy.

Checking that link

https://testjenkins.smartit.it/.well-known/acme-challenge/4rrZq8v6t9Y_tj8XGtuvH_jQmUbCkmLRbLQcZnjUZdk

the answer:

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Apache/2.4.25 (Debian) Server at testjenkins.smartit.it Port 80

An Apache port 80 answers if https is checked. Why isn't there a port 443 answer?

Please create a working port 80 configuration.

1 Like

Then there is something different in your testjenkins config file.
HTTP forwards to HTTPS for all three names and also requests to their challenge folders.
So look and compare the challenge file handlings.
Staring with the command line:

sudo docker run -it --rm --name certbot \
-v /var/www/html:/var/www/html \
-v "/etc/letsencrypt:/etc/letsencrypt" \
-v "/var/lib/letsencrypt:/var/lib/letsencrypt" \
certbot/certbot certonly \
-d www.smartit.it -d smartit.it -d testjenkins.smartit.it \
--webroot --webroot-path /var/www/html \
--expand

When using --webroot, it must be used immediately before the domain.
You used it after the domain.

hello is test but problem is redirect only https

thanks i resolve it

1 Like

ok i have generated and now its fine

image

1 Like

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