Auto-renew with certbot without stopping my nodejs server

Help
23

OK, HTTP [IPv4] redirects to HTTPS.
[IPv4] HTTPS seems to return something.

I think the problem is just IPv6.
Why do you have an IPv6 address in DNS?:
[it doesn't seem to be served by nodejs]

Name:      www.jumblgram.com
Addresses: 2a01:4f8:c2c:ea35::1
           188.245.74.241
2 Likes
24

image
image939×163 7.05 KB

this error goes away if i stop the http redirecting to https

25

yeah it isnt, should I make it handel them?

26

False sense of accomplishment.
Doing that doesn't really fix anything,
It only makes the test think that it could work because it doesn't fail outright.

2 Likes
27

Pick one [your choice]:

  • use IPv6 in DNS and serve the IPv6 requests
  • remove the IPv6 from DNS [no requests to serve]
2 Likes
28

ive removed the ipv6 from the DNS now

1 Like
29

there seems to be no errors on the Lets Debug thing now, but the renew still errors the same

1 Like
30

Good choice.
:+1:

2 Likes
32

What is the command you ran?
What was the webroot used?

2 Likes
33

sudo certbot renew --dry-run

34

The webroot must match the path [minus the /.well-known/acme-challenge/ part].

2 Likes
35

where is the webroot

1 Like
36

Where did you put that "file.txt" file?

2 Likes
37

inside acme-challenge

38

Well, that would be the FULL path.
The webroot is that same FULL path minus the /.well-known/acmne-challenge/ part.
[that part gets automatically added by the acme client]

2 Likes
39

yeah but like where actually do I input the webroot

40

certbot certonly -webroot -w /path/to/where/ever/that/is -d jumblgram.com -d www.jumblgram.com

User Guide — Certbot 2.12.0.dev0 documentation (eff-certbot.readthedocs.io)

2 Likes
41

so the path would just be /file.txt

42

What is that entire path [on the disk]?

You are confusing the HTTP request path with where the files are located on the disk PATH.

2 Likes
44

Use:

2 Likes