-
Notifications
You must be signed in to change notification settings - Fork 647
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
dyndns: cloudflare not working with some tlds #1136
Comments
|
Ideally, we'd need test credentials and a test case to fix this. No contributor uses cloudflare, so we cannot fix easily. |
|
Hey, this still seems valid... |
|
Bump bump @Nornode did you find a solution at all? |
|
is there a functional version already? just asking. i can offer testing |
|
I think here is the problem
Using "X-Auth-Key: api_token" does not seem to work with the api token We should use "Authorization: Bearer api_token" instead I have come to that conclusion after trying my api token from the command line. |
|
I removed headers X-Auth-Key and replaced with header "Authorization: Bearer api_token". I used a token with permission to list zones and it worked fine curl_setopt($ch, CURLOPT_HTTPHEADER, array(
"X-Auth-Email: {$this->_dnsUser}",
"Authorization: Bearer {$this->_dnsPass}",
'Content-Type: application/json'
)); |
|
Can you please reopen this issue? As I said replacing "X-Auth-Key:" with "Authorization: Bearer" solve the issue. There is no need for "X-Auth-Email:" |
|
it looks like it is being fixed here 7592767 :) |

CloudFlare dyndns is broken with subdomains or international TLDs with many parts (like .co.uk). The bug exists since commit opnsense/core@55586d3 . As the current code was taken from pfsense, they already have a fix for that which can be referred to. (https://redmine.pfsense.org/projects/pfsense/repository/revisions/2446fffa5932e8debcaf165bfaf5492cea429c60)
The text was updated successfully, but these errors were encountered: