starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #906] [SOLVED] Another let's encrypt Cloudflare DNS challenge with TOKEN #766

New issue

Closed

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

kerem commented

2026-02-26 06:34:19 +03:00

Owner

Originally created by @j2l on GitHub (Feb 19, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/906

Great project! Thank you!

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Are you sure you're not using someone else's docker image?
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

Describe the bug
Issuing a temporary token from Cloudflare didn't make letsencrypt happy enough:

What version of Nginx Proxy Manager is reported on the login page?
2.8.0

Screenshots

a read access is enough right?

Operating System

Rpi (Rock Pine64)

Additional context
I'm sure I didn't use a KEY 😄

Thanks!

EDIT, SOLUTION : a read access is NOT enough right, needs EDIT access to write a DNS TXT entry.
It's non sense since letsencrypt has enough with read access though API to prove it's your domain.
BTW, don't forget to delete the token and check DNS after lets encrypt did its trick.

Originally created by @j2l on GitHub (Feb 19, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/906 Great project! Thank you! **Checklist** - [x] Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - [x] Are you sure you're not using someone else's docker image? - [x] If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Describe the bug** Issuing a temporary token from Cloudflare didn't make letsencrypt happy enough: - What version of Nginx Proxy Manager is reported on the login page? - 2.8.0 **Screenshots** ![image](https://user-images.githubusercontent.com/65325/108492924-0214fe80-72a6-11eb-9f23-208fc8208bbb.png) ![image](https://i.imgur.com/CvnAxn2.png) ![image](https://user-images.githubusercontent.com/65325/108493776-02fa6000-72a7-11eb-928c-3cb33809a4f2.png) a read access is enough right? **Operating System** - Rpi (Rock Pine64) **Additional context** I'm sure I didn't use a KEY :smile: Thanks! EDIT, SOLUTION : a read access is NOT enough right, needs EDIT access to write a DNS TXT entry. It's non sense since letsencrypt has enough with read access though API to prove it's your domain. BTW, don't forget to delete the token and check DNS after lets encrypt did its trick.

kerem

2026-02-26 06:34:19 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:34:19 +03:00

Author

Owner

@Dudleydogg commented on GitHub (May 3, 2025):

Any reason why Nginx wont remember the token when selection of a new cert I have to go reset my token if I did not store it in my notes. seems like it should remember that token for each time it updates a certificate?

@Dudleydogg commented on GitHub (May 3, 2025): Any reason why Nginx wont remember the token when selection of a new cert I have to go reset my token if I did not store it in my notes. seems like it should remember that token for each time it updates a certificate?

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#766

No description provided.

Rows
Columns