[GH-ISSUE #33] internal error when trying to issue certificate. #28

Closed
opened 2026-02-26 05:33:14 +03:00 by kerem · 2 comments
Owner

Originally created by @zaywalker on GitHub (Dec 5, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/33

First of all, thanks for the npm app :)

Just like as the title, when I try to get a certificate, npm returns internal error.

The log is bellow

Command failed: /usr/bin/certbot certonly --cert-name "npm-2" --agree-tos --email "admin@example.com" --preferred-challenges "http" -n -a webroot -d "test.example.com" 


/bin/sh: 1: /usr/bin/certbot: not found

I've looked into npm container /usr/bin, there is no certbot. It looks like changed to certbot-auto.

thanks again the npm!

Originally created by @zaywalker on GitHub (Dec 5, 2018). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/33 First of all, thanks for the npm app :) Just like as the title, when I try to get a certificate, npm returns internal error. The log is bellow ``` Command failed: /usr/bin/certbot certonly --cert-name "npm-2" --agree-tos --email "admin@example.com" --preferred-challenges "http" -n -a webroot -d "test.example.com" /bin/sh: 1: /usr/bin/certbot: not found ``` I've looked into npm container /usr/bin, there is no certbot. It looks like changed to certbot-auto. thanks again the npm!
kerem closed this issue 2026-02-26 05:33:14 +03:00
Author
Owner

@jc21 commented on GitHub (Dec 5, 2018):

Ok looks like I merged something I shouldn’t have. Use the ‘2.0.6’ docker tag for the previous version for now until I fix

<!-- gh-comment-id:444382809 --> @jc21 commented on GitHub (Dec 5, 2018): Ok looks like I merged something I shouldn’t have. Use the ‘2.0.6’ docker tag for the previous version for now until I fix
Author
Owner

@jc21 commented on GitHub (Dec 9, 2018):

I've reverted the upstream changes and the latests docker images are working as expected now.

<!-- gh-comment-id:445586366 --> @jc21 commented on GitHub (Dec 9, 2018): I've reverted the upstream changes and the latests docker images are working as expected now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#28
No description provided.