Recent content by MattW

Adding the page rule to cache everything allows the bypass of the file permissions through XF and PHP, so it prevents the file being streamed from the bucket, and served directly from Cloudflare cache on the edge nodes Pasting the full URL from z22se of an image in a node which requires a user...

I have a page rule in place telling them to cache everything after /attachments/

I’ve migrated a site over from Wasabi today as well 👍

So this morning (06:50 BST), I disabled the cli job-runner addon (https://xenforo.com/community/resources/cli-job-cron-runner.7931/) and switched back to event based job triggers, and the number of Class A transactions has dropped to basically nothing now:

I don't see code_cache or temp being used in R2, they are still locally present in internal_data on the local server.

Does anyone have an idea on how much stuff is going on in the background with regards to the Class A transactions? It's not a busy site, and the number of Class A transactions seems pretty high considering the traffic the site gets.

It states in the documentation that x-amz-acl on the PutObject API function isn't implemented: https://developers.cloudflare.com/r2/data-access/s3-api/api/

I can get it working until you try to upload an attachment: Aws\S3\Exception\S3Exception: Error executing "PutObject" on "https://REDACTED.r2.cloudflarestorage.com/internal_data/attachments/23/23612-4ee7121e10de557ec13b4f9d410145f3.data"; AWS HTTP error: Server error: `PUT...

Yes it was, and that host only accepting TLS1.3 so failing with the native OS CURL version.

Correct, I can't get any CentOS7 server to connect with CURL # curl -IL https://XXX -v * About to connect() to xtest.dev port 443 (#0) * Trying 92.50.126.141... * Connected to xtest.dev (92.50.126.141) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile...

So after going through the addon code: # curl -IL https://XXX -v * About to connect() to xtest.dev port 443 (#0) * Trying 92.50.126.141... * Connected to xtest.dev (92.50.126.141) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt...

Could it be Cloudflare's Firewall that is blocking something? If I use CURL to connect to his site, I'm getting a 403 denied by the firewall and the Managed Challenge. I don't know what this addon is doing or trying to connect to though.

Yes, as part of imunify360. There are several rules that have had to be disabled, but it works fine now.

I ended up having to use SES for all the major sites I host, and then for the smaller ones setting up smart routing within EXIM to route certain addresses via Sendgrid: send_via_sendgrid: driver = manualroute domains = ! +local_domains : hotmail.com : outlook.com : live.com : yahoo.com...

Using it fine here with 10.6