[DigitalPoint] App for Cloudflare® 1.9.1.1

[Alpha1]

Is it possible to run this addon both on a main domain as well as a subdomain? i.e. domain.com and staging.domain.com
Could any issues arise from that?

 

[digitalpoint]

Yeah, it has been driving me bonkers. 18 options here:
View attachment 288310
And 18 in CF here which match the above:
View attachment 288311
Changing Account Resources to a specific account does not change anything.
In Zone Resources I can enter a specific zone in the drop down and this saves. But when editing the drop down is empty.
I did not apply IP or date filters yet.

It looks okay there, but maybe set the Zone Resources to include "All zones" rather than a specific (but blank) zone? This is what mine looks like:



If that doesn't work, maybe somehow the token is mucked on Cloudflare's side? It wouldn't hurt to simply create a new token to see if somehow that fixes it: Create token

Getting this after deleting an image and trying to upload another one in the attachments. Any suggestions?

Is it something ongoing? If there's an issue on Cloudflare's side, the addon automatically retries once, but if it fails on the retry, it will return the error being returned (that error you saw). The Cloudflare status doesn't show any issues currently going on, however a 500 error (anything in the 500-599 range) is a server-side issue (on Cloudflare's side).

 

[digitalpoint]

Is it possible to run this addon both on a main domain as well as a subdomain? i.e. domain.com and staging.domain.com
Could any issues arise from that?

Ya it should be fine.

 

[digitalpoint]

Getting this after deleting an image and trying to upload another one in the attachments. Any suggestions?

Looks like whatever it was has been resolved on Cloudflare's side. Looking in the R2 developer area of the Discord and someone reported it at 7:57 am (23 minutes ago) and it was fixed art 8:04 (7 minutes later). I guess not enough time to even create a status report. But supposedly it's fixed now.

 

[Alpha1]

If that doesn't work, maybe somehow the token is mucked on Cloudflare's side? It wouldn't hurt to simply create a new token to see if somehow that fixes it: Create token

No dice there. I'll contact CF support if they see anything.

 

[digitalpoint]

Well, they probably aren't going to be able to tell you much generally... they will want a specific API call that isn't working. There's a lot of different API calls being run in parallel on that page, but let me see if I can replicate what you are seeing if I delete a specific permission...

 

[digitalpoint]

@Alpha1 are you able to turn on XenForo debugging? You should see more useful information (like what the specific API call was that caused it)...

@Shuya https://www.cloudflarestatus.com/incidents/40qnv8mrnq1q

 

[digitalpoint]

At this point, the free version is just pending review before it gets added to wordpress.org (I submitted it on June 9, so it's been exactly 1 month so far).

View attachment 288267

For the last 2 months, they have been averaging 19 reviews per week.

Plugin Review Team: 09 Jul 2023

This is the first update from the new team. Hi! 👋 First things first: The Plugin Review team is acutely aware of how the delays caused by the current backlog are impacting plugin developers. We are…

make.wordpress.org

Based on when I submitted it and them doing 19 per week, it wouldn't get reviewed until January 16, 2024. Hopefully they figure out a solution to their backlog before then. hah

 

[Alpha1]

@Alpha1 are you able to turn on XenForo debugging? You should see more useful information (like what the specific API call was that caused it)...

Yes, here is the output:

1010: auth.forbidden

GET https://api.cloudflare.com/client/v4/zones/xxx/settings/nel

{"headers":{"Content-Type":"application\/json","Authorization":"Bearer xxx-xxx-xxx-xxx-xxx"},"query":[]}

I replaced zone code with xxx

 

[digitalpoint]

Yes, here is the output:

I replaced zone code with xxx

I've tried to replicate it, but I haven't been able to. The permission needed for that setting is Zone.Zone Settings. If I remove that permission from my token, I get an error, but it's a different error (10000: Authentication error).

When I look up Cloudflare error 1010, it's a browser integrity check issue. Not sure why that would affect API calls though... Just to test, maybe go to your Cloudflare security settings and set security level to "Essentially off" and disable "Browser integrity check"?

 

[Alpha1]

Just to test, maybe go to your Cloudflare security settings and set security level to "Essentially off" and disable "Browser integrity check"?

No dice after turning this off.

 

[digitalpoint]

Hmmm... okay I'd say go ahead and open a ticket with Cloudflare. Let them know you are getting a 1010: auth.forbidden when making an API call (and not a 10000: Authentication error). 1010 is supposed to be a browser integrity check error for normal pages, not API requests.

 

[Alpha1]

Cloudflare support asks:

Have we verified this works: https://developers.cloudflare.com/api/operations/zone-settings-get-nel-setting on a website that is not facing issues? This may be an issue with the feature availability.
I believe this has to do with the feature availability as generally this is an enterprise endpoint, this is why I want to see if this works on your other zone as well

 

[digitalpoint]

Cloudflare support asks:

Works fine for my sites, yes. Do you have any other sites you could try it on to see if it’s site specific or Cloudflare account specific?

 

[Shuya]

@Alpha1 are you able to turn on XenForo debugging? You should see more useful information (like what the specific API call was that caused it)...

@Shuya https://www.cloudflarestatus.com/incidents/40qnv8mrnq1q

You are always one step ahead. I can confirm this has been resolved now.

Thank you, @digitalpoint.

 

[Alpha1]

Works fine for my sites, yes. Do you have any other sites you could try it on to see if it’s site specific or Cloudflare account specific?

Could it be php 8.1?

 

[Aivaras]

Could it be php 8.1?

XenForo recommends PHP 8.0 and does not fully support 8.1 yet. I had issues with 8.1 while trying it out and had to revert to 8.0.

 

[digitalpoint]

Could it be php 8.1?

No, the error is coming from Cloudflare’s side.

 

[Alpha1]

CF support found the issue:

You can ignore the api call for now. The issue has to to do with the entitlements for plan types free plans have the ability to toggle the feature on and off in the dashboard, but the business plan does not have this, this is why you are seeing the error for the business zone. This is generally an enterprise feature so we will need to follow up internally on why this is shown for the free customers. You can ignore the error because this is something that should not be allowed to be changed which is why you see the error

This API call doesnt work:

[17:41][root@sin ~]# curl --request GET   --url https://api.cloudflare.com/client/v4/zones/xxxx/settings/nel   --header 'Content-Type: application/json'   --header 'X-Auth-Key: xxx'
{"success":false,"errors":[{"code":9106,"message":"Missing X-Auth-Key, X-Auth-Email or Authorization headers"}]}

 

[digitalpoint]

Weird… Free, Pro and Enterprise can toggle it but not Business. Lol makes sense…

Actually doesn’t make much sense if they turn it into an Enterprise-only thing because all it does is remove an HTTP header (the nel header). Before it was an option, I just used transform rules to remove it. So it’s still able to be removed, it’s just simpler with the toggle.