-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare key "" does not match regex "^[a-zA-Z0-9]+$"
#705
Comments
For now I'm going to pin the version I am hosting to |
Please share your config, are you using the email field? If so you must set the key field as well. That was previously a bug (AFAIK) not validating the key field (fixed from #702) |
key "" does not match regex "^[a-zA-Z0-9]+$"
Sorry for the delay {
"settings": [
{
"provider": "cloudflare",
"zone_identifier": "abc123",
"domain": "abc123",
"host": "@",
"ttl": 600,
"email": "abc123@gmail.com",
"token": "abc123",
"proxied": true
}
]
} I have the inner part copied 17 times. I have even rebuilt my config file and it still doesn't work on master. |
It has been running just fine locked on v2.6 since my previous message last week. So it must be some change between release v2.6 and master branch. |
Remove the email key. As per the documentation docs/Cloudflare.md if you set an email, you're also expected to set a key. There is no need to set an email for the other authentication methods. |
TLDR: Describe your issue in a one liner here
Is this urgent: Yes
DNS provider(s) you use: N/A
Program version: ae4ab39
What are you using to run the container: Docker, through Unraid Community Apps.
Extra information (optional)
Logs:
Configuration file (remove your credentials!):
N/A
Host OS: Unraid 6.12.6
This was running correctly on the previous commit of this. My config file hasn't changed since August 2023.
The text was updated successfully, but these errors were encountered: