mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1665] Cloudflare invalid credentials #1243
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#1243
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 @aniel300 on GitHub (Dec 21, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1665
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
when i tried to renew ssl cert i get "internal error". note: am using wildcard with Cloudflare.
Nginx Proxy Manager Version
latest as the time of this posting
To Reproduce
Steps to reproduce the behavior:
Expected behavior
be able to renew cert which also bring me to a question. isn't npm supposed to auto do this ?
Screenshots
https://i.imgur.com/3KpuUjy.png
Operating System
ubuntu 18/docker
Additional context
i did tried to find a similar issue to this and found some but i cant figure out if there is a fix for this or not
some post i found:
https://github.com/jc21/nginx-proxy-manager/issues/1659
https://github.com/jc21/nginx-proxy-manager/issues/1625
thank you in advance.
@chaptergy commented on GitHub (Dec 21, 2021):
Have a look at https://github.com/jc21/nginx-proxy-manager/issues/1271, especially the certificate section and provide some the letsencrypt logs, otherwise the issue could be anything.
@aniel300 commented on GitHub (Dec 21, 2021):
ok will do sir, is it safe to share my logs here ?
@chaptergy commented on GitHub (Dec 21, 2021):
The only sensitive information in the letsencrypt logs should be the domain and maybe the email address you entered as the notification address. You can search and replace them with placeholders if you like. The other information is ramdomly generated challenge data which is useless by the time you have posted the logs.
@lildevilx commented on GitHub (Dec 22, 2021):
Hello,
I'm also having some issues and hoping you could give me some assistant,
here is my log.
Letsencrypt Logs
Thanks!
@chaptergy commented on GitHub (Dec 22, 2021):
@lildevilx Your issue seems to be related to your docker container being misconfigured and not being able to connect to the internet / a dns server. Have a look at https://github.com/jc21/nginx-proxy-manager/issues/1482 or https://github.com/jc21/nginx-proxy-manager/issues/1365.
@RonnieBlaze commented on GitHub (Dec 28, 2021):
I am having the same issue when trying to manually renew my cerfts, I have 11 days left on them, so it looks like the auto renew has not been work either. I am running NPM v2.9.13 in a unraid docker, using cloudflare for dns,
My docker log shows this,
certbot logs show
@aniel300 commented on GitHub (Dec 29, 2021):
sorry for my ignorance where is it that i find the required logs ? maybe here ?: \docker\proxymanager\data\logs
@aniel300 commented on GitHub (Dec 29, 2021):
here is the docker logs, let me know if u need anything else and also if i have included any sensible info.
Docker Logs
@chaptergy commented on GitHub (Dec 29, 2021):
@aniel300 Your logs say
Have you provided valid credentials?
@aniel300 commented on GitHub (Dec 29, 2021):
Yes. this wildcard cert was created by the first host i did.
@chaptergy commented on GitHub (Dec 29, 2021):
Then your issue is either related to https://github.com/jc21/nginx-proxy-manager/pull/1697, or it is not an npm issue at all. Go ahead and try using docker image
jc21/nginx-proxy-manager:github-pr-1697. If that does not work, try it with your own installation of certbot to see if that works.EDIT: sorry, I got confused by all the different issues in this thread, forgot that you are the original author.
@chaptergy commented on GitHub (Dec 29, 2021):
It could also be possible that the reason is the slightly changed namespace syntax in certbot. You should connect to the database, go to the
certificatetable, and themetacolumn for your certificates row should contain your credentials. Make sure it saysdns_cloudflare_api_token = ...and not something likecertbot-dns-cloudflare:dns_cloudflare_api_token = ...@aniel300 commented on GitHub (Dec 29, 2021):
ahh ok. so does this response still valid ?
@chaptergy commented on GitHub (Dec 29, 2021):
Sure, so first check the database, if that does not work try the different docker image, and if that still does not work try it with a custom certbot installation on a different machine.
@aniel300 commented on GitHub (Dec 29, 2021):
i can try to do few of those things except for the one of using a different machine since this is a dedicated server
@christofkac commented on GitHub (Dec 30, 2021):
Hi,
I don't know if this is related but I ran into the same problem.
It is important to configure your DNS entry In Cloudflare as "DNS only" as long as you don't have a certificate and once the certificate is created, switch to "Proxied".
Hope that helps
@aniel300 commented on GitHub (Dec 31, 2021):
@christofkac i tried with dsn only and issue still happening
@github-actions[bot] commented on GitHub (Feb 29, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@aniel300 commented on GitHub (Mar 21, 2024):
closing as i never got it fix or got the time to attempt to fix it. long time has passed and I now use traefik. still this project is amazing for pp looking to get into reverse proxies and want/ need a ui to help them trough the journey. thank u to the devs and keep up the good work.