digitalpoint
Well-known member
There's an internal option that stores your Cloudflare Account ID (can see it on the debug options page if you have debugging enabled).
The error you see would be because the account ID isn't set (it's important that it's set).
Normally it's all automatic, but there is a mechanism where the addon would erase the value that is set there. Specifically, if an API request is made and Cloudflare returns a 10000 error (which is an authentication error... meaning your API token credentials are not correct). The intent is that it will pick up the correct account ID once the issue resolves itself (the token has permissions to work with it).
If you set secondary restrictions on your token (for example only certain IPs can use it), you really should remove that restriction... because if your server ever makes a request from an IP you didn't whitelist, the API request will fail because you told Cloudflare to only allow the token to be used from a specific IP. It will cause nothing but problems... additionally, IP restrictions can't be used with presigned URLs unless you are whitelisting the IPs of your users (which obviously can't realistically be the case).
If it's only an issue with whatever "future post" thing you are doing, maybe somehow it's doing those from a different IP than the server normally uses (like maybe it's being pushed to a cron job that runs elsewhere). But again... save yourself future headaches and disable IP restrictions on token usage if you put one in place.
The error you see would be because the account ID isn't set (it's important that it's set).
Normally it's all automatic, but there is a mechanism where the addon would erase the value that is set there. Specifically, if an API request is made and Cloudflare returns a 10000 error (which is an authentication error... meaning your API token credentials are not correct). The intent is that it will pick up the correct account ID once the issue resolves itself (the token has permissions to work with it).
If you set secondary restrictions on your token (for example only certain IPs can use it), you really should remove that restriction... because if your server ever makes a request from an IP you didn't whitelist, the API request will fail because you told Cloudflare to only allow the token to be used from a specific IP. It will cause nothing but problems... additionally, IP restrictions can't be used with presigned URLs unless you are whitelisting the IPs of your users (which obviously can't realistically be the case).
If it's only an issue with whatever "future post" thing you are doing, maybe somehow it's doing those from a different IP than the server normally uses (like maybe it's being pushed to a cron job that runs elsewhere). But again... save yourself future headaches and disable IP restrictions on token usage if you put one in place.