Recent content by digitalpoint

If it's a brand new domain (sounds like it if you are just deleting it and readding it), maybe wait a day or two... I haven't experienced it firsthand, but I'd seen random blurbs where API access is weird on new zones for the first 24-48 hours.

Stupid question, but not sure what else to look at... maybe try setting the limitation you have set to a specific account (Account Resources) to instead be "All accounts"?

Assuming the settings page still is giving you an error, but you are able to verify the token with that curl command at the same time, the only other thing I can think of would be if certain individual API calls were having an issue. Maybe double/triple check your API token permissions? Maybe...

Is that from the same server that your site is running on?

@Matt C. if you have shell access to your server, here's a basic cURL request that will simply test if your API token is valid: curl https://api.cloudflare.com/client/v4/user/tokens/verify -H 'Authorization: Bearer YOUR-API-TOKEN-HERE' If you run that, what do you get?

If that's really the case, only Cloudflare could resolve that... but I highly doubt it. You are talking about a setting that would affect browsers accessing your site. There's no setting you can set that would affect your server's ability to access api.cloudflare.com (you also can't reconfigure...

Well like I said, there's nothing you can configure in Cloudflare to block your outbound network access to api.cloudflare.com (what is happening underneath it all), even if you wanted to. So it's not a Cloudflare setting you set. Maybe double check your API token... like did you put any...

There shouldn't be any setting you can set that would block yourself from the API... Your server is communicating with the Cloudflare API, not itself, so...

Did it work itself out? Specifically, if you are changing a ton of settings fairly quickly, you could end up being rate limited. The Cloudflare API allows 1200 API requests per 5 minute window. It takes approximately 20 API calls to build the page and about the same number whenever you change a...

Rocker Loader shouldn’t be on with XenForo, but that won’t prevent the settings from working.

Right... so you need to make sure your server supports TLS 1.2 or TLS 1.3 if you want it to be able to talk to servers that only allow that (for example Cloudflare API).

@Matt C. one thing that updating old versions of cURL will give you is support for newer TLS versions. As an example api.cloudflare.com (and most modern sites these days) have disabled support for SSLv2, SSLv3, TLS 1.0 and TLS 1.1. So if your version of cURL doesn't supports TLS 1.2 or TLS 1.3...

Usually that's going to be an old/outdated version of cURL or outdated root certificates on your server. The link it gives you tells you those for error 35:

Well, not sure what to tell you... if your server admins are refusing to give you a server that can (always) resolve DNS queries, I know what I would do (switch to a better host). Not only is 8.8.8.8 rate-limited by Google, using an external DNS server (external to your server's data center) is...

Well, I was just saying that because YOU couldn't resolve api.cloudflare.com from the server (outside of the addon). See: Maybe don't confuse them by saying it's specific to the addon. They don't need to debug the addon... the server wasn't able to resolve api.cloudflare.com even when NOT...