SSL Renew Issue

Help
1

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: .com

I ran this command: certbot renew --force-renewal --config-dir cert/

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

My web server is (include version): tomcat on docker container

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

My hosting provider, if applicable, is:

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 1.32.2

4

Hi @Peter7, and welcome to the LE community forum :slight_smile:

First, don't use this without knowing what it does:

It will not force something that is broken to be fixed.

Please show the outputs of:
certbot certificates
cat /root/MappingSite/cert/renewal/www.pyinnyar-subuu.com.conf

3 Likes
6

version shows as 0.40.0. But i have already updated to 1.32.2

7

Please show:
netstat -pant | grep -i listen | grep 80

2 Likes
9

You can ignore the numbers shown in the renewal config files - that was the version that created the file.

Please also show:

And also show:
curl -4 ifconfig.io

2 Likes
12

That is the right IP.
And I don't see anything listening on port 80.

What shows?:
certbot certificates

2 Likes
13

Sorry I over looked .

Saving debug log to /var/log/letsencrypt/letsencrypt.log

No certificates found.

15

hmm...
Your topic says "Renew" and your command includes "renew".
What happened to the certificate?

2 Likes
16

Not from where I use the Internet.
All I see is "error 400":

curl -Ii4 http://www.pyinnyar-subuu.com/anything
HTTP/1.1 400
Content-Type: text/plain;charset=UTF-8
Connection: close

Is the NAT correct?
[same as port 443]

2 Likes
18

Did you delete the certificate?

2 Likes
21

Wait a minute!
That shows the NAT going to port 8080 [wWhich is help by Docker].
Are you running certbot in the right container?

2 Likes
24

How was it set when you last renewed?

Yeah, I got 400 for every HTTP request.

2 Likes
25

It worked as per normal.

26

You should never port forward 80 to 443.

Nothing "normal" there.

Revisit your notes.

3 Likes
27

noted i will revert back to previous rules

1 Like
28

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