[DigitalPoint] App for Cloudflare® 1.9.1.1

[digitalpoint]

It does actually (I just tested it and it appears to be working). You need to use the "Spam cleaner" option there, and it has to be IP address(es) that have been used by the user in the last 30 days. When I tested it on a spam user, the 3 IPs they used show up in the Cloudflare firewall rules:

 

[Chromaniac]

weird. i would double check the next time a spammer gets stuck in moderation queue! thanks.

right now, i try to mark them as spam from their posted content. because they never appear in firewall if i mark them as spammer from the moderation queue. would verify again.

 

[digitalpoint]

A couple things you can check... make sure the option to do it is enabled (under Options -> External service providers -> Block IP addresses on spam clean from user approval queue), make sure they have IP addresses logged in the last 30 days (if you aren't recording IPs for example it won't do anything, or if they have been in the queue for an extended period of time without any IPs being used recently).

 

[Ivancas]

Can somebody share let me know why the bucket created for data by the addon can't load?
If I try to access the data bucket created in another domain, the following screen confirms the R2 url loads:


However, in another domain/cloudflare account I get the following error when I try to access the R2 url:


Could it be a problem on CloudFlare end? I can't explain why, if both buckets are created from the addon, one works and the other doesn't.

 

[digitalpoint]

Did you do the things the error message mentions? Like did you manually create a DNS record for it or anything (you shouldn’t)?

 

[Ivancas]

Did you do the things the error message mentions? Like did you manually create a DNS record for it or anything (you shouldn’t)?

No, everything was done automatically by the addon as usual. I’ve tried creating several buckets with different names to find out a pattern but I didn’t have luck

 

[digitalpoint]

Hard to say without seeing your DNS records. If you look at the DNS for the domain in Cloudflare, if the R2 public hostname is anything other than a record type of “R2”, someone did something funky/manually and whatever that DNS record (CNAME, A, etc) needs to be deleted. Only R2 DNS record types are valid for R2 buckets.

 

[Ivancas]

Hard to say without seeing your DNS records. If you look at the DNS for the domain in Cloudflare, if the R2 public hostname is anything other than a record type of “R2”, someone did something funky/manually and whatever that DNS record (CNAME, A, etc) needs to be deleted. Only R2 DNS record types are valid for R2 buckets.

It’s r2 and linked to the bucket, your addon does it automatically. Like I said, I run the bucket creation with your addon so I don’t know why it isn’t working

 

[digitalpoint]

Ya not sure… maybe something internal going on with Cloudflare? Could delete the public domain from your R2 setup in Cloudflare and re-add it. Beyond that, not sure… would need to open a a ticket with Cloudflare maybe if redoing it doesn’t fix it.

 

[ivp]

Not specific to Cloudflare, but I've definitely seen more general networking issues with IPv6 vs. IPv4

As you assumed, after started using IPv4 for outbound traffic, the situation is significantly better. I'm pretty sure that clearing the cache via cron job also helped a lot. Thanks for that!

In the meantime, received reply from Cloudflare after 17 days of opening the ticket:

looking at the trace it seems there was an intermittent issue with slight packet loss.

the timeout seeing error "cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received seems to indicate that the request did not reach Cloudflare.

Are you still seeing some issues with purging?

This can be considered non-existent support for Pro account. I'm worried if it is good idea to rely on them, because nobody is there to help with any issue.

 

[digitalpoint]

As you assumed, after started using IPv4 for outbound traffic, the situation is significantly better. I'm pretty sure that clearing the cache via cron job also helped a lot. Thanks for that!

Great! I ended up disabling IPv6 on my servers years ago. Was just too problematic with random issues. I’m sure it’s probably getting better over time, but I haven’t bothered to revisit it again yet. Maybe in 10 years when equipment is up to par and network admins have figured it out a little better. Hah

In the meantime, received reply from Cloudflare after 17 days of opening the ticket:


This can be considered non-existent support for Pro account. I'm worried if it is good idea to rely on them, because nobody is there to help with any issue.

Well it’s a tough thing for them to resolve on their end. They can’t solve network traffic issues on equipment or data centers they have no control over. So doesn’t particularly surprise me… would have been nice if it was a quicker response though.

 

[Alpha1]

@digitalpoint R2 storage is interesting. Do you also use R2 storage for WordPress? And if so what plugin do you use? So far I only found the media cloud plugin but it has rather bad reviews and I cannot imagine that you would ever install such code ever. So that makes me wonder what if anything do you use for WP R2?

 

[Chromaniac]

It's coming! (His WordPress addon for Cloudflare) stuck in review

 

[digitalpoint]

@Alpha1 ya… the WordPress version of this addon is identical feature-wise. It is split into a free/premium version (it’s a lot of work building for WordPress and I don’t personally have a need for it myself, so…). Using R2 for media storage is one of the functions that landed on the premium side of the fence.





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).

 

[Forsaken]

@Alpha1 ya… the WordPress version of this addon is identical feature-wise. It is split into a free/premium version (it’s a lot of work building for WordPress and I don’t personally have a need for it myself, so…). Using R2 for media storage is one of the functions that landed on the premium side of the fence.

View attachment 288265

View attachment 288266

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

Does that mean someone could pay for the premium version now?

 

[digitalpoint]

Does that mean someone could pay for the premium version now?

No, the premium version requires the free version to be installed (the premium version isn't a stand-alone plugin, rather it extends the functionality of the free version). So because of that and to just keep things simple with trying to distribute the free version some place other than wordpress.org, I'm just sitting tight until it's approved. When that time comes, it will be here (not publicly accessible currently): https://appforcf.com/

 

[Alpha1]

I'm encountering a weird issue. The CF API token works. The addon displays 1010: auth.forbidden on /admin.php?cloudflare/
All other addon pages work fine and display data that was pulled in by the API. There are no error logs.

 

[digitalpoint]

I'm encountering a weird issue. The CF API token works. The addon displays 1010: auth.forbidden on /admin.php?cloudflare/
All other addon pages work fine and display data that was pulled in by the API. There are no error logs.

Double/triple check the token permissions match what is shown on the Options -> External service providers page (where you enter your token). At this point, there are 18 permissions that the token should have.

 

[Alpha1]

Yeah, it has been driving me bonkers. 18 options here:

And 18 in CF here which match the above:

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.

 

[Shuya]

DigitalPoint\Cloudflare\Api\Exception\Server: Server error: DELETE https://74fc47a9449c59027cd076dadb825071.r2.cloudflarestorage.com/internaldata-attachments-laleagane/attachments/22/22508-3e947ccc1f7fcaf960389c415b207a22.data resulted in a 500 Internal Server Error response: <?xml version="1.0" encoding="UTF-8"?><Error><Code>InternalError</Code><Message>We encountered an internal error. Please (truncated...) in src/addons/DigitalPoint/Cloudflare/Traits/XF.php at line 90

1. DigitalPoint\Cloudflare\Api\Cloudflare->request() in src/addons/DigitalPoint/Cloudflare/Api/Cloudflare.php at line 562
2. DigitalPoint\Cloudflare\Api\CloudflareAbstract->makeRequest() in src/addons/DigitalPoint/Cloudflare/Api/Advanced.php at line 795
3. DigitalPoint\Cloudflare\Api\Advanced->deleteR2Object() in src/addons/DigitalPoint/Cloudflare/League/Flysystem/Adapter/R2.php at line 157
4. DigitalPoint\Cloudflare\League\Flysystem\Adapter\R2->delete() in src/vendor/league/flysystem/src/Filesystem.php at line 237
5. League\Flysystem\Filesystem->delete()
6. call_user_func_array() in src/vendor/league/flysystem-eventable-filesystem/src/EventableFilesystem.php at line 431
7. League\Flysystem\EventableFilesystem\EventableFilesystem->callFilesystemMethod() in src/vendor/league/flysystem-eventable-filesystem/src/EventableFilesystem.php at line 395
8. League\Flysystem\EventableFilesystem\EventableFilesystem->delegateMethodCall() in src/vendor/league/flysystem-eventable-filesystem/src/EventableFilesystem.php at line 330
9. League\Flysystem\EventableFilesystem\EventableFilesystem->delete() in src/vendor/league/flysystem/src/MountManager.php at line 533
10. League\Flysystem\MountManager->delete() in src/XF/Util/File.php at line 237
11. XF\Util\File::deleteFromAbstractedPath() in src/XF/Service/Attachment/Preparer.php at line 90
12. XF\Service\Attachment\Preparer->insertDataFromFile() in src/addons/Truonglv/ImageOptimizer/XF/Service/Attachment/Preparer.php at line 31
13. Truonglv\ImageOptimizer\XF\Service\Attachment\Preparer->insertDataFromFile() in src/XF/Service/Attachment/Preparer.php at line 38
14. XF\Service\Attachment\Preparer->insertAttachment() in src/XF/Attachment/Manipulator.php at line 199
15. XF\Attachment\Manipulator->insertAttachmentFromUpload() in src/XF/Pub/Controller/Attachment.php at line 91
16. XF\Pub\Controller\Attachment->actionUpload() in src/XF/Mvc/Dispatcher.php at line 352
17. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
18. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
19. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
20. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2487
21. XF\App->run() in src/XF.php at line 524
22. XF::runApp() in index.php at line 20

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