# Issue getting certificate with NPM **URL:** \ **Category:** Help\ **Created:** [September 3, 2024, 3:39pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149 "2024-09-03T15:39:22Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![andsim](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andsim/32/82526_2.png) [@andsim](https://community.letsencrypt.org/u/andsim)\ **Post date:** [September 3, 2024, 3:39pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/1 "2024-09-03T15:39:22Z")
here log i got i am on npm too > **[2024-09-03 15:21:48,841:DEBUG:certbot.\_internal.main:certbot version: 2.11.020...](https://pastebin.com/HBMjC8MG)** > > Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time. ---
**Author:** ![andsim](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andsim/32/82526_2.png) [@andsim](https://community.letsencrypt.org/u/andsim)\ **Post date:** [September 3, 2024, 3:53pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/2 "2024-09-03T15:53:32Z")
it come two version, first it will use sqlite by default, or download with database version.. ---
**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\ **Post date:** [September 4, 2024, 2:33am UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/3 "2024-09-04T02:33:20Z")
@andsim we can't be sure you error is the same but the error in your log file is ```nohighlight 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](http://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. ---
**Author:** ![andsim](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andsim/32/82526_2.png) [@andsim](https://community.letsencrypt.org/u/andsim)\ **Post date:** [September 4, 2024, 1:01pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/4 "2024-09-04T13:01:55Z")
DNS is working fine what is wrong wth error when i look thru web browser > ERR\_ADDRESS\_INVALID ---
**Author:** ![andsim](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andsim/32/82526_2.png) [@andsim](https://community.letsencrypt.org/u/andsim)\ **Post date:** [September 4, 2024, 1:10pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/5 "2024-09-04T13:10:04Z")
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](http://acme-v02.api.letsencrypt.org) > Pinging [ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com](http://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 ---
**Author:** ![andsim](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andsim/32/82526_2.png) [@andsim](https://community.letsencrypt.org/u/andsim)\ **Post date:** [September 4, 2024, 1:25pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/7 "2024-09-04T13:25:51Z")
here > "hostname": "andsimgaming.ca", > "port": "80", > "addressesResolved": [ > "192.124.249.15" > ], > "addressUsed": "192.124.249.15" > addressused is wrong ip ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [September 4, 2024, 4:26pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/8 "2024-09-04T16:26:39Z")
> [@andsim](#): > > addressused is wrong ip How is that the wrong IP? ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [September 4, 2024, 4:34pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/9 "2024-09-04T16:34:53Z")
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](https://crt.sh/?q=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): ---
**Author:** ![Nightwalker83](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nightwalker83/32/82506_2.png) [@Nightwalker83](https://community.letsencrypt.org/u/Nightwalker83)\ **Post date:** [September 4, 2024, 6:49pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/10 "2024-09-04T18:49:31Z")
I am just trying to set an ssl cert up for local access rather than over the internet. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [September 4, 2024, 6:56pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/11 "2024-09-04T18:56:58Z")
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. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [September 4, 2024, 11:30pm UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/12 "2024-09-04T23:30:40Z")
Do you require a globally signed cert for that? If not, then a long-lived self-signed cert should do the trick nicely. ---
**Author:** ![Nightwalker83](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nightwalker83/32/82506_2.png) [@Nightwalker83](https://community.letsencrypt.org/u/Nightwalker83)\ **Post date:** [September 5, 2024, 12:57am UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/13 "2024-09-05T00:57:40Z")
I am not sure! Looking in to other options at the moment. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [October 5, 2024, 12:58am UTC](https://community.letsencrypt.org/t/issue-getting-certificate-with-npm/225149/14 "2024-10-05T00:58:37Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.