Issue getting certificate with NPM

Help
1

here log i got
i am on npm too

2

it come two version, first it will use sqlite by default, or download with database version..

3

@andsim we can't be sure you error is the same but the error in your log file is

2024-09-03 15:21:48,908:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/directory.
2024-09-03 15:21:48,910:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org:443
...
...
ssl.SSLError: [SSL: TLSV1_UNRECOGNIZED_NAME] tlsv1 unrecognized name (_ssl.c:992)

This appears to be saying that your system cannot resolve the DNS name acme-v02.api.letsencrypt.org to an IP address, so you need to investigate how DNS resolution works in nginx proxy manager. I would advise contacting nginx proxy manager support.

3 Likes
4

DNS is working fine what is wrong wth error when i look thru web browser

ERR_ADDRESS_INVALID

5

i ran ping test
at first it was bloc thank to pihole. but i unblock it
second ping test went fine
C:\Users\andsi>ping acme-v02.api.letsencrypt.org

Pinging ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com [172.65.32.248] with 32 bytes of data:
Reply from 172.65.32.248: bytes=32 time=2ms TTL=59
Reply from 172.65.32.248: bytes=32 time=2ms TTL=59
Reply from 172.65.32.248: bytes=32 time=2ms TTL=59
Reply from 172.65.32.248: bytes=32 time=2ms TTL=59

7

here

"hostname": "andsimgaming.ca",
"port": "80",
"addressesResolved": [
"192.124.249.15"
],
"addressUsed": "192.124.249.15"
addressused is wrong ip

8

How is that the wrong IP?

3 Likes
9

I agree with Rudy; your DNS servers say the IP address for andsimgaming.ca is 192.124.249.15.

That said, I fail to see how @andsim s problem is related to @Nightwalker83 s problem. (This isn't like, the all-encompassing NPM-thread..) So I'll move the last few posts to a new thread.

Also:

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:

I ran this command:

It produced this output:

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):

4 Likes
10

I am just trying to set an ssl cert up for local access rather than over the internet.

11

Let's Encrypt needs to be able to verify the hostname through the public internet using either HTTP on port 80 (redirects to HTTPS on port 443 are allowed) using the http-01 challenge, port 443 (using the rather complicated tls-alpn-01 challenge) or through the public DNS using the dns-01 challenge.

2 Likes
12

Do you require a globally signed cert for that?
If not, then a long-lived self-signed cert should do the trick nicely.

3 Likes
13

I am not sure! Looking in to other options at the moment.