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: *.xolm-ph.com
I ran this command:
It produced this output:
My web server is (include version): NGINX
The operating system my web server runs on is (include version): Debian GNU/Linux 11 (bullseye)
My hosting provider, if applicable, is:
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): Portainer
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Hi, I'm running an Nginx Reverse Proxy in a Docker.
Trying to add a Let's Encrypt SSL and I'm getting this error:
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-14" --agree-tos --email "xxx@gmail.com" --domains "*.xxxx-yy.com,homelab.xxxx-yy.com" --authenticator dns-google-domains --dns-google-domains-credentials "/etc/letsencrypt/credentials/credentials-14"
An unexpected error occurred:
pkg_resources.VersionConflict: (zope.interface 5.4.0 (/tmp/npmuserhome/.local/lib/python3.7/site-packages), Requirement.parse('zope.interface>=5.5.0'))
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-63q1__vq/log or re-run Certbot with -v for more details.
at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
Hi @xomanuel, and welcome to the LE community forum
Please take the time to answer the questions below - which you should have been presented with when choosing the "Help" category:
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. 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):
Let me first state that I personally have the opinion NPM is a terrible piece of software, as it usually makes debugging Certbot/certificate issues really difficult. I would never advice anyone to use it.
That said, can you please provide your Docker settings? I.e., Dockerfile et cetera. Be aware it might be something we can't help fixing. It looks like an incompatibility between installed Python packages and this might be something only NPM can fix. But we'd need to have more information.
I would never recommend that: looks like with that command you'd install stuff on your base system with pip globally: so neither within the NPM container nor within a virtual environment!
