Getting a certificate via NPM doesn't work

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: minepanel.shinecraft.ru and other

I ran this command: I wanted to get a certificate from the Nginx Proxy Manager WEB interface

It produced this output: at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

My web server is (include version): nginx in nginx proxy manager

The operating system my web server runs on is (include version): ubuntu 24.04

My hosting provider, if applicable, is: hsvds.ru

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): Nginx Proxy Manager

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

Yes, sadly NPM does not show any of the useful error messages your system was given by the Let's Encrypt authentication server. There is nothing you show that helps us.

We see NPM problems often and they almost always are setup problems related to NPM itself. You would do better at the NPM support channels.

The only advice I have is to check the AAAA record in your DNS. It does not seem to point to the openresty (nginx) server used within NPM. Or, perhaps the openresty is not setup to listen on IPv6 properly.

4 Likes