[DigitalPoint] App for Cloudflare® 1.8.2

[MaximilianKohler]

Anyone else seeing this error?
workers.api.error.entitlement (Code: 10014)



This is the only thing I can find about it https://community.cloudflare.com/t/cloudflare-workers-error-code-10014/520989, and there's not much info.

 

[digitalpoint]

Anyone else seeing this error?
workers.api.error.entitlement (Code: 10014)

View attachment 293467

I saw it a bunch earlier but it didn’t seem to matter for what I was doing. The entitlement endpoint just gives info about what your account can do (is entitled to) as far as Cloudflare services. I think they use it to show or hide different things in the dashboard navigation.

 

[Chromaniac]

but maybe they are for whatever reason.

heh yeah. blog.cloudflare.com gives that error. cloudflare.com is fine. forces me to create bbcode for the link. small annoyance.

 

[ichpen]

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.

View attachment 293465

And the workers update just uses cloudflare's new recommended ES module style of code instead of their older service worker style. Cloudflare claims the module style to be more efficient, but it probably isn't too significant.

As for getting it to update, I had to disable the image proxy in the XF App, then go to my workers in Cloudflare dash, delete the worker for the image proxy, and then go back into the XF App and re-enable the image proxy. That automatically updated the url proxy worker as well.

I didn't think this addon actually created and deployed workers on CF at all unless @digitalpoint got all fancy on us recently.

 

[Chromaniac]

they might not appear instantly. but they do appear for me after a few minutes. same thing happened when i cleaned up old workers and reenabled the option after latest update as suggested by dev to migrate to the new mechanism being used now! i can even see stats now though i never noticed old workers having stats though i could be mistaken!

 

[digitalpoint]

I didn't think this addon actually created and deployed workers on CF at all unless @digitalpoint got all fancy on us recently.

It does… for the option where you can use Workers as image and unfurl proxies to hide your server IPs (requests come from Cloudflare IPs).

 

[ichpen]

It does… for the option where you can use Workers as image and unfurl proxies to hide your server IPs (requests come from Cloudflare IPs).

Aha did not even go there, good to know.

 

[⭐ Alex ⭐]

Hi digitalpoint, will you support sending forum emails using Cloudflare in the App for Cloudflare via MailChannels?

Send email using Workers with MailChannels

MailChannels has created an email sending service specifically for Cloudflare Workers that removes all the friction associated with sending emails

blog.cloudflare.com

 

[digitalpoint]

Not planned, no. If they ever support sending email directly with a Worker and not just using a Worker for a third party commercial service, maybe.

There’s really no reason to use a Worker with Mailchannels unless you are building an app on top of Workers and need to send email from within that app. Why use a Worker as an API endpoint when you can just use Mailchannels as the endpoint?

 

[fly]

I just turned on R2 and ran the migration, but am seeing broken avatar thumbnails. What am I missing?

 

[digitalpoint]

Hard to say without knowing the URL. If you migrated existing avatars with something other than the tool it comes with (the cmd.php CLI tool), most likely whatever tool you used put them in the wrong place in the R2 bucket. The “paths” are important. See this post:

[DigitalPoint] App for Cloudflare®

...as far as what to check on the Cloudflare side, go to SSL/TLS settings. If you have it set to Off or Flexible, the traffic between Cloudflare and your server might not be secure. Best to do Full or Full (strict) assuming your web server can handle secure connections (Full allows you to use...

xenforo.com

 

[fly]

Hard to say without knowing the URL. If you migrated existing avatars with something other than the tool it comes with (the cmd.php CLI tool), most likely whatever tool you used put them in the wrong place in the R2 bucket. The “paths” are important. See this post:

[DigitalPoint] App for Cloudflare®

...as far as what to check on the Cloudflare side, go to SSL/TLS settings. If you have it set to Off or Flexible, the traffic between Cloudflare and your server might not be secure. Best to do Full or Full (strict) assuming your web server can handle secure connections (Full allows you to use...

xenforo.com

Apologies, I used your native CLI tool.

 

[digitalpoint]

Can you post a screenshot of a listing of some of the files in the bucket from the Cloudflare dashboard?

 

[fly]

So this is probably a big clue. The URL looks like this, which doesn't work:

/avatars/s/0/1.jpg?1607981201

But if I take that string off the end, it works fine.

/avatars/s/0/1.jpg

 

[fly]

Can you post a screenshot of a listing of some of the files in the bucket from the Cloudflare dashboard?

 

[digitalpoint]

So this is probably a big clue. The URL looks like this, which doesn't work:

/avatars/s/0/1.jpg?1607981201

But if I take that string off the end, it works fine.

/avatars/s/0/1.jpg

Can you post one of the avatar’s full URLs?

 

[digitalpoint]

@fly the URL you sent me works for me (even with the number in it). My guess is you had the external data URL set before the data was actually moved and it's cached in your browser from a request your browser made before it was moved to R2 and/or it's cached in Cloudflare's network edge for the same reason. Try flushing your browser cache, and if that doesn't fix it for you, purge the Cloudflare cache for your zone.

 

[fly]

dammit. I had done a hard refresh and it hadn't fixed it. But of course hadn't tried another browser. Apologies, consider this fixed.

 

[digitalpoint]

digitalpoint updated [DigitalPoint] App for Cloudflare® with a new update entry:

API calls for settings are run in parallel

• The API calls necessary to build the Cloudflare settings page are now run in parallel (it's currently 10 API calls that were previously made sequentially). Viewing (and editing) settings is significantly faster now (it's as fast as the single slowest API call, rather than as slow as all 10 API calls added together).
• Added more sanity checks for unexpected Cloudflare API results
• Fixed issue where old public domains wouldn't get enabled when setting up R2 bucket for...

Read the rest of this update entry...

 

[Digital Doctor]

This addon is a full time job.