How to change SSL certificate from terminate server?

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: sudo certbot --nginx

It produced this output: Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Type: connection
Detail: Fetching Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): Nginx

The operating system my web server runs on is (include version): Ubuntu(idk only i know is it is the newest)

My hosting provider, if applicable, is: DigitalOcean for server and for dns Nitrado

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 2.7.4

This error message is pretty clear, isn't it? The Let's Encrypt server can't connect to you via HTTP on port 80, the most likely reason being a firewall. You need to fix this.


I'm unable to reach your site via HTTP:

curl -Ii
curl: (56) Recv failure: Connection reset by peer

Let's Debug also can't reach your site via HTTP: Let's Debug (
Using Let's Debug is a very easy way for you to test if your site is reachable or not.


Of the Challenge Types - Let's Encrypt consider changing to the DNS-01 challenge instead of the HTTP-01 challenge as there still has been no change (likely a firewall) in being able to access the domain name.

$ nmap -Pn -p80,443
Starting Nmap 7.80 ( ) at 2023-11-06 23:04 UTC
Nmap scan report for (
Host is up.

80/tcp  filtered http
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 3.85 seconds
1 Like

hey the ip thats in () is from the terminatet server but idk how to change it

Sounds like you need to change the DNS entry for to point to your new server IP address.


thx thats work


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