NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
PR60X Cloudflare DDNS
I am getting an "Authentication unsuccessful" for my Cloudflare DDNS. I have tested my api token so I know it works. I think it may be the username. I have tried my email address tied to the api token, like the flavor text recommends. I have also tried my username, my Cloudflare Account ID, the default "Bearer". I think the username should be blank but the router will not let me.
I have tried with both types of Cloudflare api tokens (user and account). Any help on this is highly appreciated.
The "Authentication unsuccessful" error in router-based DDNS setups is frequently caused by the router using an outdated Global API Key protocol rather than the modern API Token standard. If your router requires a username and won't let you leave it blank, it is likely expecting your Cloudflare email address paired with your Global API Key (found under My Profile > API Tokens), rather than a scoped Bearer token. If you must use a scoped API Token and the router demands a username, try entering token or bearer as a placeholder, but be aware that many older router firmwares simply do not support the Authorization Header format required for new tokens and will only work with the Global Key.
4 Replies
The "Authentication unsuccessful" error in router-based DDNS setups is frequently caused by the router using an outdated Global API Key protocol rather than the modern API Token standard. If your router requires a username and won't let you leave it blank, it is likely expecting your Cloudflare email address paired with your Global API Key (found under My Profile > API Tokens), rather than a scoped Bearer token. If you must use a scoped API Token and the router demands a username, try entering token or bearer as a placeholder, but be aware that many older router firmwares simply do not support the Authorization Header format required for new tokens and will only work with the Global Key.
Yup that was it! My router wanted the full email address and the Global API key. I also corrected the "Domain" field. I removed my purchased domain name and instead placed my NS (Name Server). In my case the NS was "domaincontrol.com". Thank you for maritn for your help!
Just a note: Beside using email / Global API key to authenticate with Cloudflare, Zone ID/Token authentication is also supported. Please check Cloudflare Zone ID for details.
Thanks c3po - I just checked and it works great!
FYI forget my earlier post. Instead of a Name Server, the router wants a subdomain. So for future visitors of this forum, the "Domain" field, do "home@example.com" or something of the like. Here is what I did for my A record in Cloudflare:
Type: A
Name: home
Content: current public IP
TTL: Auto
Proxy: OFF
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
