![[DigitalPoint] App for Cloudflare®](/community/data/resource_icons/8/8750.jpg?1692633961){kind=icon}
Because this thread has literally hundreds of users subscribed to it and they probably don't want to be getting push notifications/alerts/emails every time someone has a random Cloudflare question unrelated to the addon this thread is for. I'm happy to help with Cloudflare account questions when I can, but not in this thread. This thread is already busy enough, so best to keep it related to the addon.
https://mybucket.xxxxx.com/xfmg/thumbnail/0/49-8b7f3cb6dce3c196ecb1b306762c608c.jpg?1693938397https://mybucket.xxxxx.com/media/my-old-system.49/full?d=1698780922
), but having these added would probably help others who aren't comfortable navigating Cloudflare.
xenforo.com
That probably has something to do with the power outage Cloudflare suffered yesterday. Some things still appear to be down. You can read more about it, including info from @digitalpoint, starting here:
Cloudflare optimizations for XenForo
Are you on the Pro plan? (Or can't I find these stats?) Yes, I am one of the lucky ones that signed up with CF years ago when the new player in the CDN world and they grandfather the super low cost pro plan until this day. It appears that some of what I posted is a pro only feature.
www.cloudflarestatus.com
Maybe on their website, but doubtful if it’s your website. The main thing being impacted is you can’t change your Cloudflare settings/config reliably.
Is there anything we would need to change on our end if we're already using R2 and cloudflare workers + image proxy?
The deep links are these links to the cloudflare dashboard, Cloudflare just updated the URL so they didn't exactly work correctly until digitalpoint fixed them just now.
It's not really necessary. It's more just for new setups. But if you want to move to the ES Module style code, you can do as mentioned above (disable them, delete the Workers in Cloudflare and more or less start new and it will offer to create the Workers for you). But honestly, not really worth the effort. Not really going to make any difference whatsoever imo.
blog.cloudflare.com
Could not fetch metadata from URL with error: Response returned a non-successful status code: 403. And I am using this add-ons proxy which uses Cloudflare 
xf-url-proxy, xf-image-proxy), and at some point I created the 3rd one (xfimageproxy). I can't find info about it on the Overview or FAQ pages of this addon. xfimgproxy.mysite.com. Its DNS record is:And the page
xfimgproxy.mysite.com loads with a "hello world" message.
403 is forbidden... not sure why they would be blocking it, but maybe they are for whatever reason.Details have arrived!
Post mortem on the Cloudflare Control Plane and Analytics Outage
Beginning on Thursday, November 2, 2023 at 11:43 UTC Cloudflare's control plane and analytics services experienced an outage. Here are the details
For some weird reason Cloudflare links do not unfurl on my board. They do here. Testing showsCould not fetch metadata from URL with error: Response returned a non-successful status code: 403. And I am using this add-ons proxy which uses Cloudflare
xfimageproxy was never created by this addon. You can grep for that string and it doesn't exist in the addon, so no clue where that came from... probably someone made it manually? If it's a "Hello World" message, it's just a default Worker with the default code it plops in when you manually create a Worker. If you aren't using it for something, it should be safe to delete it. It has nothing to do with this addon either way.
