nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard

Fails to add a let's encrypt certificate via DNS for digital ocean provider.

Open AlexMakesSoftware opened this issue 3 years ago • 4 comments

I am using jc21/nginx-proxy-manager:latest on Raspbian 11 bullseye, and I'm trying to generate a wildcard certificate for NPM to use.

When attempting to add a let's encrypt certificate using the nice friendly GUI, I find it produces a red 'internal error' box with an error as follows (top of extract):

Error: Command failed: pip install certbot-dns-digitalocean==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') 
  error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [123 lines of output]

I will attach the details in a text file.

This is a brand new install, installed yesterday.

Nginx Proxy Manager Version is v2.9.16

To Reproduce Steps to reproduce the behavior:

  1. Log in
  2. CLick on SSL Certs, Add
  3. Enter wildcard domain name *.yourdomain.com
  4. Make sure you click to add it just below where you entered the domain.
  5. Enter a a valid email
  6. TIck use DNS Challenge.
  7. Choose digital ocean from providers list.
  8. Go to digital ocean (cloud.digitalocean.com), log in and click API, generate new token
  9. Set the token to your wildcard domain name (*.yourdomain.com)
  10. Set expires: never,
  11. Tick write access, then generate.
  12. Click 'copy' just tot he right of the key.
  13. Go back to the NPM screen and paste the key (replacing the existing code) after the 'token=' bit of the credentials area.
  14. Tick agree and then SAVE.
  15. Do nothing, just wait for the error.

Expected behavior I expected it to contact Digital Ocean using the API key I gave it.

System Rpi 2B OS: Raspbian 11 bullseye Kernel: armv7l Linux 5.10.92-v7+ CPU: ARMv7 rev 5 (v7l) @ 4x 900MHz RAM: 922MiB

Additional context

details.txt

AlexMakesSoftware avatar Feb 21 '22 10:02 AlexMakesSoftware

I have exactly the same error/bug trying to setup ssl via cloudflare. The error report is attached and identical to the one of the previous poster.

Same steps as mentioned by previous poster lead to this error.

System Rpi 3B OS: Raspian 10 buster Kernel: Linux raspberrypi 5.10.63-v7+ CPU: ARMv7 Processor rev 4 (v7l) RAM: 922MiB

NPM_certbot-error.txt

muchachooo avatar Mar 02 '22 00:03 muchachooo

Same issue here via Digital Ocean. Version NPM → 2.9.18 Raspbian GNU/Linux 11 (bullseye)

NPM_letsencrypt_error.txt

tucker457 avatar May 27 '22 15:05 tucker457

Same issue for CloudFlare OS : Ubuntu 22.04 Kernel : 5.15.0-33-generic CPU : Intel i5-6500T NPM Version : v2.9.18

Error: Command failed: pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') cloudflare
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-cloudflare/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-cloudflare/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-cloudflare/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-cloudflare/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-cloudflare/
ERROR: Could not find a version that satisfies the requirement certbot-dns-cloudflare==1.25.0 (from versions: none)
ERROR: No matching distribution found for certbot-dns-cloudflare==1.25.0

    at ChildProcess.exithandler (node:child_process:399:12)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

Kaorw avatar May 29 '22 11:05 Kaorw

Same issue trying to use Cloudfare Nginx Proxy Manager v2.9.18 OS: Raspbian GNU/Linux 11 (bullseye)

Error: Command failed: pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') cloudflare
  error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1

fernoliveros avatar Jul 05 '22 17:07 fernoliveros

Same issue here. Fresh docker install and I am getting this. Anyone ever going to answer here?

Fyb3roptik avatar Nov 03 '22 18:11 Fyb3roptik

Issue is now considered stale. If you want to keep it open, please comment :+1:

github-actions[bot] avatar Feb 23 '24 01:02 github-actions[bot]

I long since abandoned this project but it would be nice if the author of this project could at least take a look at this bug and comment -even if the comment was 'I cannot reproduce this error'.

AlexMakesSoftware avatar Feb 26 '24 10:02 AlexMakesSoftware