digitalpoint
Well-known member
R2 is storage, it doesn't alter anything. No idea what "[tg]Image Optimizer" is, but maybe others do?
![[DigitalPoint] App for Cloudflare®](/community/data/resource_icons/8/8750.jpg?1692633961){kind=icon}
[DigitalPoint] App for Cloudflare® 1.9.1.1
- Thread starter digitalpoint
- Start date
securedme
Well-known member
R2 is storage, it doesn't alter anything. No idea what "[tg]Image Optimizer" is, but maybe others do?
digitalpoint
Well-known member
Like I said, R2 is just storage... you can use whatever you want to modify an image before it's stored. R2 itself does not alter anything (if that's your question)?
duderuud
Well-known member
Getting quite a few errors like this:
Something going on at Cloudflare?
Code:
ErrorException: Cloudflare: 10000: Authentication error src/XF/Error.php:81
Generated by: Unknown account May 8, 2025 at 12:54 PM
[HEADING=2]Stack trace[/HEADING]
#0 src/XF.php(266): XF\Error->logError('Cloudflare: 100...', false)
#1 src/addons/DigitalPoint/Cloudflare/Traits/XF.php(162): XF::logError('Cloudflare: 100...')
#2 src/addons/DigitalPoint/Cloudflare/Api/Cloudflare.php(701): DigitalPoint\Cloudflare\Api\Cloudflare->logError('Cloudflare: 100...')
#3 src/addons/DigitalPoint/Cloudflare/Api/Cloudflare.php(584): DigitalPoint\Cloudflare\Api\CloudflareAbstract->makeRequest('POST', 'zones/54056b25e...', Array, Array)
#4 src/addons/DigitalPoint/Cloudflare/Repository/Cloudflare.php(1274): DigitalPoint\Cloudflare\Api\CloudflareAbstract->purgeCache('54056b25e599ef6...', Array)
#5 src/addons/DigitalPoint/Cloudflare/Job/PurgeCache.php(15): DigitalPoint\Cloudflare\Repository\CloudflareAbstract->purgeCache(Array)
#6 src/XF/Job/Manager.php(275): DigitalPoint\Cloudflare\Job\PurgeCache->run(8)
#7 src/XF/Job/Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
#8 src/XF/Job/Manager.php(89): XF\Job\Manager->runJobEntry(Array, 8)
#9 job.php(46): XF\Job\Manager->runQueue(false, 8)
#10 {main}Something going on at Cloudflare?
Last edited:
LemmeSeeHim
Member
I'm getting the same errors. It must be a cloudflare system issue.
digitalpoint
Well-known member
Is it still happening? I checked a few of my sites and I haven't seen any errors going on. Maybe Cloudflare was having an issue that resolved itself?
kontrabass
Well-known member
Got the same errors, latest was about an hour ago. Will report back if still occuring
digitalpoint
Well-known member
Were your errors also on the purgeCache API call? Haven't seen an official incident, but was going to ask directly and wanted to make sure they are all happening with the same purgeCache API call.
LemmeSeeHim
Member
Got the same error at around 3pm EST
duderuud
Well-known member
The last error was about 14 hours ago so it seems fixed @ Cloudflare.
kontrabass
Well-known member
Does seem to be fixed 
ichpen
Well-known member
Anyone getting a bunch of these? I just lost all my images from R2. No errors, they occasionally come back, no backend errors but I sense CF is having some probs.
<Error>
<Code>ExpiredRequest</Code>
<Message>Request has expired</Message>
<div style="all: initial !important;"/>
</Error>
<Error>
<Code>ExpiredRequest</Code>
<Message>Request has expired</Message>
<div style="all: initial !important;"/>
</Error>
digitalpoint
Well-known member
Are you using presigned URLs? They are only valid for a short period of time.
ichpen
Well-known member
Yes I am.... Should I be doing something ? First time I see the issue.
EDIT: I unchecked it and they started rendering. Been using this for over a year and has never seen these expire in such a way.
digitalpoint
Well-known member
Is the time/date on your server correct?
ichpen
Well-known member
On paper it should be as I've not so much as rebooted for a while but I'll check it out tomorrow, thanks for chiming in. They would sporadically show strangely enough.
ichpen
Well-known member
Interestingly enough was off by 61 seconds, somehow. Anyway, I've left presigned URLs off for now, might try again later.
digitalpoint
Well-known member
It would make sense since the server is building a URL that's good for 60 seconds. When you are off by exactly that amount, sometimes it will work, sometimes it wont (since you are coming within microseconds of it being expired).
It's VERY important that your server time is correct if you are going to use presigned URLs since it's generating a unique URL that expires 60 seconds in the future. If the server thinks it's more than 60 seconds earlier than it actually is, it's going to be generating URLs that have expired in the past (already expired).
ichpen
Well-known member
Great advice and I sense this is what went wrong here.
