-
Notifications
You must be signed in to change notification settings - Fork 3.1k
unkown NGINX-proxy-manager error while creating ssl-certificate #4529
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
Comments
我也是一样,不知道什么问题 |
I don’t understand. |
Hi! @BulldozerPete did you manage to find a solution? i have the same problem. I keep getting internal error when i try to generate a new ssl certificate, or when i try to renew the old one, |
No solution yet. |
@BulldozerPete any work arounds? coming close to a mass of sites expiring |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug

I would like to create an SSL certificate in NGINX Proxy manager, but will run in same error.
My config looks like this.
The api-key will be inserted from IPV64 user about for domain.provider.com
Nginx Proxy Manager Version
v2.12.3
To Reproduce
Steps to reproduce the behavior:
`Internal Error
CommandError: error: subprocess-exited-with-error
× Building wheel for certbot-dns-multi (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [41 lines of output]
/tmp/pip-build-env-mxvyzg7q/overlay/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning:
project.license
as a TOML table is deprecated!!
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for certbot-dns-multi
[notice] A new release of pip is available: 25.0.1 -> 25.1.1
[notice] To update, run: pip install --upgrade pip
ERROR: Failed to build installable wheels for some pyproject.toml based projects (certbot-dns-multi)
Expected behavior
Screenshots
Operating System
RaspberryPiOS
Additional context
The text was updated successfully, but these errors were encountered: