-
Notifications
You must be signed in to change notification settings - Fork 19
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
Not able to connect with cloudflare API #4
Comments
I have no idea, sorry. Can you provide some steps on how you got your API key from Cloudflare? My API key has Zone edit permissions, that might be a cause? Howe old is your API key? |
On your API key, if you click the dropdown box, there's a That's the permission my API key has, and it works for me. Maybe @jgrahamc can connect us with someone that can help if that's not the case. I'm not an expert in their permissions, sorry! |
Yes it has that permission. Concerning the ZoneId, you found it in the web url while being on the dns tab of the cloudflare website right? |
Okay, I found the issue, I'm sorry, my ZoneId was incorrect, I thought it was the key on the url but it seems not. Maybe the documentation could be improved to tell where is the ZoneId located on cloudflare website. I could make a PR for that if you want. |
Sure, if you want to make a PR for it, that'd be great. :) |
Hi, I got the same issue. I've checked that the zone id is correct. In some way the request is malformed as the HTTP 400 suggest. |
So I made a massive update recently, and I'm also getting the HTTP 400 errors, but I'm not 100% sure why. I did some debugging but I didn't see anything that stood out. I'll keep an eye on it, but if you could try the most recent update, that'd be great. Thanks! |
When I put the Clouflare Api Key, I got that error
cannot get upstream records: error from makeRequest: HTTP status 400: content "{"success":false,"errors":[{"code":6003,"message":"Invalid request headers","error_chain":[{"code":6111,"message":"Invalid format for Authorization header"}]}],"messages":[],"result":null}"
Any idea where it could come from?
The text was updated successfully, but these errors were encountered: