Type: unauthorized

[thytith]

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 only makes it harder for us to provide help.

My domain is: dpcloud.dpdatacenter.com

I ran this command: certbot certonly --webroot -w /var/www/html/owncloud -d dpcloud.dpdatacenter.com

It produced this output:
ertbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: dpcloud.dpdatacenter.com
Type: unauthorized
Detail: 157.10.72.9: Invalid response from https://dpcloud.dpdatacenter.com/.well-known/acme-challenge/iU2EoimlP5fnDdUaGrQYGnQRiCfkJgSzzYh2FqOxAIo: 502
My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

[MikeMcQ]

Welcome @thytith

You already got a cert and your system responds to HTTPS requests with a 502 Bad Gateway error. This is caused by some kind of problem with your proxy statements in nginx (probably). The destination of the proxy is probably not running or accessible.

I get the same 502 error for requests to your "home" page. You should fix that first. You don't need to get another cert.

curl -i https://dpcloud.dpdatacenter.com
HTTP/1.1 502 Bad Gateway
Server: nginx/1.18.0 (Ubuntu)

[thytith]

thank you
I will double checked it

[webprofusion]

I believe "Bad Gateway" often means that your front end server (e.g. nginx) is proxying back to a backend service and that the backend service isn't answering.

For the actual http domain validation though is there a reason you are using the webroot method (serving the challenge response via your web application file system) instead of certbots built in nginx method?