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.
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" --preferred-challenges "dns,http" --domains "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. 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):
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
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. A DNS challenge might succeed if you setup the TXT records correctly.
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?
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.