mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1955] SSL duckdns internal error #1417
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1417
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @El-mou33 on GitHub (Mar 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1955
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Internal SSL error
Nginx Proxy Manager Version
Version 3
To Reproduce
Steps to reproduce the behavior:
Expected behavior
An ssl should appear.
Screenshots
Operating System
Raspberry pi 4B+ running OMV 6 (Open Media Vault 6)
Additional context
Error: Command failed: pip install certbot-dns-duckdns~=0.6
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [123 lines of output]
Collecting setuptools>=40.6.0
Downloading setuptools-61.1.0-py3-none-any.whl (1.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 8.3 MB/s eta 0:00:00
Collecting wheel
Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Collecting cffi>=1.12
Using cached cffi-1.15.0.tar.gz (484 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting setuptools-rust>=0.11.4
Using cached setuptools_rust-1.2.0-py3-none-any.whl (21 kB)
Collecting pycparser
Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting typing-extensions>=3.7.4.3
Using cached typing_extensions-4.1.1-py3-none-any.whl (26 kB)
Collecting semantic-version<3,>=2.8.2
Using cached semantic_version-2.9.0-py2.py3-none-any.whl (15 kB)
Building wheels for collected packages: cffi
Building wheel for cffi (setup.py): started
Building wheel for cffi (setup.py): finished with status 'error'
error: subprocess-exited-with-error
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
WARNING: You are using pip version 22.0.3; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
@csibe1999 commented on GitHub (Mar 27, 2022):
Same to me on RP 3b+
@El-mou33 commented on GitHub (Mar 29, 2022):
Could be a problem if I have home assistant hassio observer on the 4357:80 port?
@lee5i3 commented on GitHub (Mar 29, 2022):
I'm getting the same thing with my RPI 4, fresh install with docker.. however I'm using Route53
Maybe its the OS, im using Raspberry Pi OS Lite (32-bit)
arch: armv7l
@pablosanjose commented on GitHub (Apr 1, 2022):
I had the same issue, also rpi4/arm7. There are some missing dependencies to build the certbot-dns-duckdns hook. I opened a terminal into the docker instance, and ran the following:
It takes a good while to finish, but it fixed the issue. Is there any way to received the compiled hook already with the docker image?
@El-mou33 commented on GitHub (Apr 1, 2022):
I solved the issue. There was problems with other certificates. In Open Media Vault I had a manual ssl. In home assistant I had the duckdns addon with a lets encrypt certificate.
To solve it I do this:
In home assistant I uninstalled the addon duckdns, I use the file editor addon and I deleted the let's encrypt from the configuration.yaml
In open media vault I deleted the ssl.
I rebooted the system.
I open the 443 and 80 ports in my router.
And I set up the duckdns by docker compose on portainer.
I still having the issue :(
@lafe commented on GitHub (Apr 3, 2022):
Sames issue for me with Joker as the provider and a DNS challenge. Nginx-Proxy-Manager runs with Docker on my Raspberry Pi 4 with Raspbian 10 (buster) (Kernel version "Linux 5.10.63-v7l+ armv7l").
Docker-Compose:
The complete error message is very similar to the one posted by @El-mou33:
@technoKotsos commented on GitHub (Apr 4, 2022):
I solved the issue,
First Update .
apt update
apt-get install build-essential libssl-dev libffi-dev python3-dev cargo
pip install certbot-dns-duckdns~=0.6
Second , add SSL certificate WITHOUT usisng DNS challenge.
I am using Cloudflare.
@lafe commented on GitHub (Apr 5, 2022):
That's not really a fix if you have to update the container (changes will be gone after the next container update) and you have to avoid the feature itself. DNS challenge is required in some scenarios when the machine in question is not exposed directly to the internet and therefore unreachable by Let's Encrypt for verification purposes.
@Kaan88 commented on GitHub (Apr 9, 2022):
This worked well but when I recreated the container it got stuck in a loop of installing dns challenge packages. This process never finished, it ran for more than 12 hours and in the meantime I couldn't access the web interface. (Actual proxy stuff did work though)
For some reason it always tries to install dns challange packages (probably because I have a letsencrypt certificate) unsuccessfully and basically my installation is broken, I'll just go to a previous backup with no loss in my case.
@DeltaTangoLima commented on GitHub (Apr 10, 2022):
Unfortunately for me, this was my first attempt at using this project, so I haven't been able to get it up and running successfully on my rpi3 at all. I've gone back a few releases in the repo but am still having the same issue. Trying to install the dependencies, as others have suggested here, just takes forever on my poor li'l rpi3.
Can anyone recommend a particular container release that doesn't have this issue, please?
@El-mou33 commented on GitHub (May 7, 2022):
The problem still happening. But by the moment we can use and create ssl certificates for duckdns domains without selecting any dns challenge. Just request a new ssl, add your email, accept the terms and click save. This works more or less, you will have an ssl but browsers will alert you that it isn't a secure place.
@enthusedamateur commented on GitHub (May 31, 2022):
I'm having the same problem mentioned in #2070 but as also mentioned in there, I believe these have a related root cause.
@lgaudreau commented on GitHub (Jun 20, 2022):
Still having this issue with Cloudflare and a wildcard cert.
@vascozorrinho commented on GitHub (Aug 25, 2022):
Same problem here! any permanent fix?
@Rubix3D commented on GitHub (Aug 30, 2022):
Raspi 3B with Nginx and Cloudflare with the same error
@vascozorrinho commented on GitHub (Aug 30, 2022):
THIS helped me for clouldflare
@loznic89 commented on GitHub (Sep 4, 2022):
same issue here with odroid N2 armv7
@El-mou33 commented on GitHub (Oct 16, 2022):
IT IS SOLVED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
@321row123 commented on GitHub (Apr 13, 2023):
Sigo con el mismo error trabajando HaOS 2023.4.4 , complento Duckdns Current version: 1.15.0. No puedo ejecutar el complemento Nginx Proxy Manager Current version: 0.12.3, por conexion externa y con conexion local https://IPlocalHA:81, accedo pero en el proceso de creacion del certificado nuevamente el mismo error: Error: Command failed: pip install certbot-dns-duckdns~=0.9 SOLUCION PLEASE¡¡¡¡¡¡¡¡¡
@fcaronte commented on GitHub (May 20, 2024):
Thanks as today's this fix is needed and work correctly 💪🏻