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:depotrace.com
I ran this command:certbot certificates
It produced this output:no certificates found
My web server is (include version):
The operating system my web server runs on is (include version):linux
My hosting provider, if applicable, is:Google cloud
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):mobaxterm
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):2.6.0
But my problem is, before i hosted my application Digital Ocean and deployed ssl certificate the domain there.but now i moved my application from digtial ocean to Google Gloud and want to deploy certificate for the same domain
Why do you think this is a problem? Because it isn't. As long as you've updated DNS to point to your new IP address, you're fine--unless you've created too many certificates and have blown a rate limit.
You can have several certificates for the same identical domain. You can only get 5 a week, tho. Is this your error message?
No, it's not.
$ podman run -i docker.io/certbot/certbot certonly --standalone --register-unsafely-without-email --agree-tos -d depotrace.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for depotrace.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: depotrace.com
Type: unauthorized
Detail: 34.100.154.254: Invalid response from http://depotrace.com/.well-known/acme-challenge/YvM55xygjwlbI9_pc0RVHe7x7TnLigyuHU3uJDZaFco: "<!DOCTYPE html>\n<html lang=\"en\">\n <head>\n <meta charset=\"utf-8\" />\n <link rel=\"icon\" href=\"/favicon.ico\" />\n <meta nam"
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
Please give the complete, exact error message--because neither certbot nor Let's Encrypt will give this error message. And without knowing what it's telling you, all we can do is guess at the problem.
Edit: and contrary to both this statement and @9peppe's findings, I don't find any evidence that you've ever had a cert, from any certificate authority, for this domain name.
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
You have a react express system responding on HTTP (port 80). You would need to stop that before using the standalone authenticator as that requires exclusive use of port 80. Can you use --webroot instead and leave that running?
Notice the beginning of the html response below matches what is shown in the error message for standalone.
curl -i depotrace.com
HTTP/1.1 200 OK
X-Powered-By: Express
Date: Sat, 26 Aug 2023 18:36:29 GMT
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<link rel="icon" href="/favicon.ico" />
...(omitted)...
name="description"
content="Web site created using create-react-app"
I have followed your instruction and installed ssl certificates successfully but when my react application is running www.depotrace.com:3000 instead of depotrace.com