# Can't get cert in npm **URL:** \ **Category:** Help\ **Created:** [August 21, 2022, 7:46am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145 "2022-08-21T07:46:36Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 21, 2022, 7:46am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/1 "2022-08-21T07:46:36Z")
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: [http://srimuang.ddns.net](http://srimuang.ddns.net) I ran this command: ##### Test Server Reachability It produced this output: Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-7" --agree-tos --authenticator webroot --email "[chat\_4432@hotmail.com](mailto:chat_4432@hotmail.com)" --preferred-challenges "dns,http" --domains "[srimuang.ddns.net](http://srimuang.ddns.net)" Saving debug log to /var/log/letsencrypt/letsencrypt.log Some challenges have failed. Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. ``` at ChildProcess.exithandler (node:child_process:399:12) at ChildProcess.emit (node:events:526:28) at maybeClose (node:internal/child_process:1092:16) at Socket. (node:internal/child_process:451:11) at Socket.emit (node:events:526:28) at Pipe. (node:net:687:12) ``` ## My web server is (include version): nginx proxy manager v2.9.18 The operating system my web server runs on is (include version): debian 11 bulleye My hosting provider, if applicable, is: no-ip 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): ## The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): ---
**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:** [August 21, 2022, 6:34pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/2 "2022-08-21T18:34:58Z")
> [@chatofking](#): > > --authenticator webroot That needs a webroot path for that domain. See: [https://eff-certbot.readthedocs.io/en/stable/using.html#webroot](https://eff-certbot.readthedocs.io/en/stable/using.html#webroot) ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 23, 2022, 2:48pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/3 "2022-08-23T14:48:15Z")
i need to use this command in nginx proxy manager or cli ? ---
**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:** [August 23, 2022, 6:01pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/4 "2022-08-23T18:01:59Z")
I don't use NPM, so I can't say for sure. But it looks like your CLI command is missing part of the required arguments. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 23, 2022, 6:19pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/5 "2022-08-23T18:19:09Z")
> [@chatofking](#): > > /var/log/letsencrypt/letsencrypt.log Can you upload this log file? You have not shown enough to see the cause of the failure. Did you know your site cannot be reached with HTTP or HTTPS? If you are relying on the HTTP challenge for getting a cert this is a problem. ```nohighlight curl -i -m 10 http://srimuang.ddns.net curl: (28) Connection timed out after 10000 milliseconds ``` ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 24, 2022, 4:14am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/6 "2022-08-24T04:14:47Z")
sorry i can't -bash: cd: letsencrypt: No such file or directory [Directory '/var/log/letsencrypt' does not exist] ---
**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:** [August 24, 2022, 5:08pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/7 "2022-08-24T17:08:24Z")
Try finding that file, with: `find / -name letsencrypt.log` ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 26, 2022, 1:56am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/8 "2022-08-26T01:56:30Z")
$ sudo find / -name letsencrypt.log ```nohighlight /var/lib/docker/overlay2/e0f67f639a5d50d919438922c765b31a128490db7ef4631857a673520399bd99/merged/var/log/letsencrypt/letsencrypt.log /var/lib/docker/overlay2/e0f67f639a5d50d919438922c765b31a128490db7ef4631857a673520399bd99/diff/var/log/letsencrypt/letsencrypt.log ``` $ cd /docker `-bash: cd: /docker: No such file or directory` ---
**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:** [August 26, 2022, 3:37am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/9 "2022-08-26T03:37:01Z")
hmm... `Docker`. Are you in the right container? ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 26, 2022, 2:35pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/10 "2022-08-26T14:35:39Z")
i just using portainer how should i get ssl ? ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 27, 2022, 3:40am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/11 "2022-08-27T03:40:55Z")
i explore my volume /volume1/docker/nginx/data/logs $ ls fallback\_access.log letsencrypt-requests\_access.log proxy-host-1\_access.log proxy-host-2\_access.log fallback\_error.log letsencrypt-requests\_error.log proxy-host-1\_error.log proxy-host-2\_error.log which file ?? ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 27, 2022, 3:53am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/12 "2022-08-27T03:53:26Z")
> [@chatofking](#): > > Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-7" --agree-tos --authenticator webroot --email "XXX" --preferred-challenges "dns,http" --domains "`srimuang.ddns.net`" > > Saving debug log to **/var/log/letsencrypt/letsencrypt.log** I don't know where NPM would put the debug log stated in this message. You might ask on an NPM forum. The command says to use the webroot authenticator which uses HTTP challenge. But, I still cannot connect to your site using an http request. See also [Let's Debug test site](https://letsdebug.net/srimuang.ddns.net/1164175). A DNS challenge might succeed if you setup the TXT records correctly. ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 29, 2022, 1:24pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/13 "2022-08-29T13:24:46Z")
i try docker cp **/var/log/letsencrypt/letsencrypt.log** inside docker container but when i try to upload it show `Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, go, js, txt, pcap, pcapng, pem).` in 0 kb size what should I do ?? can you explain those challenges & TXT records? ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 29, 2022, 8:46pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/14 "2022-08-29T20:46:18Z")
> [@chatofking](#): > > Sorry, the file you are trying to upload is not authorized Can you make a copy of the log file as a `.txt` file and upload that? > [@chatofking](#): > > can you explain those challenges & TXT records? See this [Let's Encrypt topic](https://letsencrypt.org/docs/challenge-types/) about challenge types The certbot docs for that are here [https://eff-certbot.readthedocs.io/en/stable/using.html#dns-plugins](https://eff-certbot.readthedocs.io/en/stable/using.html#dns-plugins) ---
**Author:** ![chatofking](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@chatofking](https://community.letsencrypt.org/u/chatofking)\ **Post date:** [August 30, 2022, 8:35am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/15 "2022-08-30T08:35:27Z")
i can't upload even txt can you help me,what I am wrong/missing up I use this guide to setup > **[Cómo crear tu Blog con Ghost + MySQL + Nginx Proxy Manager en tu NAS](https://hdsplus.co/como-crear-tu-blog-con-ghost-mysql-nginx-proxy-manager-en-tu-nas/)** > > Guía completa que permitirá crear tu Blog con dominio propio en tu NAS con la última versión de Ghost y servicio de Newsletter activado > **[Cómo instalar y configurar Nginx Proxy Manager en tu NAS](https://hdsplus.co/como-instalar-y-configurar-nginx-proxy-manager-en-tu-nas/)** > > Guía detallada sobre cómo instalar tu Proxy Inverso en un NAS con certificado Let's Encrypt. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 30, 2022, 8:40am UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/16 "2022-08-30T08:40:40Z")
You could also use sites e.g. [https://pastebin.com/](https://pastebin.com/) for the log. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 30, 2022, 1:51pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/17 "2022-08-30T13:51:09Z")
> [@chatofking](#): > > can you help me,what I am wrong/missing up > I use this guide to setup I cannot read that guide because it requires an account at HDS. We would be happy to look at a certbot log and give advice. Osiris suggested yet another way to do that. But, I think your problem is larger and involves docker, NPM, and maybe other pieces on your system. You may be better off asking at an NPM forum as it is often difficult to use. Or, even a docker forum. People at either of those may be able to help configure your overall system. I say this because you don't have anything working from the public internet yet. As I noted back in post #5 I can't reach your site using HTTP (port 80). And, I don't see you have port 443 open for HTTPS either. These are basic things that need to be working first. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [September 29, 2022, 1:52pm UTC](https://community.letsencrypt.org/t/cant-get-cert-in-npm/183145/18 "2022-09-29T13:52:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.