[GH-ISSUE #219] How to get DNS working? #190

Closed
opened 2026-02-26 06:31:19 +03:00 by kerem · 1 comment
Owner

Originally created by @ghostbitmeta on GitHub (Oct 27, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/219

Hi,

So I did the following:

apt-get -y install python3-pip
pip3 install certbot-dns-cloudflare==`certbot --version|awk '{print $2}'`
mv ~/.config/letsencrypt/cli.ini ~/.config/letsencrypt/cli.ini.old

Then I edited /app/src/backend/internal/certificate.js so that it has:

let cmd = certbot_command + ' certonly --dns-cloudflare --dns-cloudflare-credentials /data/cloudflare.ini --dns-cloudflare-propagation-seconds 60 -d ' + certificate.domain_names.join(',')

After restarting the docker and trying to get a cert, the log prints:

[10/27/2019] [2:17:54 AM] [SSL      ] › ✔  success   IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/xxxxxx.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/xxxxxx.com/privkey.pem
   Your cert will expire on 2020-01-25. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
 - If you like Certbot, please consider supporting our work by:
   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le
[10/27/2019] [2:17:54 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[10/27/2019] [2:17:54 AM] [Express  ] › ⚠  warning   Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-8/fullchain.pem -subject -noout
x509: Cannot open input file /etc/letsencrypt/live/npm-8/fullchain.pem, No such file or directory
x509: Use -help for summary.
)

Any ideas what else I need to hack?

Originally created by @ghostbitmeta on GitHub (Oct 27, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/219 Hi, So I did the following: ``` apt-get -y install python3-pip pip3 install certbot-dns-cloudflare==`certbot --version|awk '{print $2}'` mv ~/.config/letsencrypt/cli.ini ~/.config/letsencrypt/cli.ini.old ``` Then I edited `/app/src/backend/internal/certificate.js` so that it has: `let cmd = certbot_command + ' certonly --dns-cloudflare --dns-cloudflare-credentials /data/cloudflare.ini --dns-cloudflare-propagation-seconds 60 -d ' + certificate.domain_names.join(',')` After restarting the docker and trying to get a cert, the log prints: ``` [10/27/2019] [2:17:54 AM] [SSL ] › ✔ success IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/xxxxxx.com/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/xxxxxx.com/privkey.pem Your cert will expire on 2020-01-25. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le [10/27/2019] [2:17:54 AM] [Nginx ] › ℹ info Reloading Nginx [10/27/2019] [2:17:54 AM] [Express ] › ⚠ warning Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-8/fullchain.pem -subject -noout x509: Cannot open input file /etc/letsencrypt/live/npm-8/fullchain.pem, No such file or directory x509: Use -help for summary. ) ``` Any ideas what else I need to hack?
kerem 2026-02-26 06:31:19 +03:00
Author
Owner

@chaptergy commented on GitHub (May 11, 2021):

A lot has changed with the certificates since this was opened. If you are still experiencing any issues, please open a new issue.

<!-- gh-comment-id:838932236 --> @chaptergy commented on GitHub (May 11, 2021): A lot has changed with the certificates since this was opened. If you are still experiencing any issues, please open a new issue.
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#190
No description provided.