Cloudflare Developers•8mo ago

账户无法登陆，邮箱不能用了接收不到验证码怎么解决

Aaabb 账户无法登陆，邮箱不能用了接收不到验证码怎么解决

Hard@Work•5/20/25, 4:22 PM

?login-help

SuperHelpflare•5/20/25, 4:22 PM

These links may help, but they only work when logged out. You can always use an Incognito Window or a Private Window to ensure you're logged out.

If you know the email: https://dash.cloudflare.com/forgot-password
If you know the email and have 2FA or email delivery issues: https://dash.cloudflare.com/login-help
If you don't know the email: https://dash.cloudflare.com/forgot-email

HHard@Work ?login-help

aabbOP•5/20/25, 4:23 PM

是的

aabbOP•5/20/25, 4:26 PM

邮箱不能使用了，无法接受到验证码，该如何登陆

Aaabb 邮箱不能使用了，无法接受到验证码，该如何登陆

Hard@Work•5/20/25, 4:27 PM

Try the second link the bot sent

aabbOP•5/20/25, 4:30 PM

好的我尝试一下

aabbOP•5/20/25, 4:51 PM

发送之后你们什么时候回给我答复

aabbOP•5/20/25, 5:42 PM

Hello there,
I'm sorry to hear you are having trouble logging into your account.
We're happy to help you regain access by temporarily removing the email factor authentication requirement.
To help us confirm you’re authorized to make this change, perform one of the options below:
Option 1: Create a file on your web server.
Please create a file at /.well-known/cf-2fa-verify.txt with the following content for 5 of your active domains (or all your active domains if you have less than 5): (/.well-known/cf-2fa-verify.txt for example)
S6TnbBap4SoiS9NcL4K9
After completing this task, verify that the URL works and that the token is correct.
Your server must be configured to serve files from hidden directories. If /.well-known is treated specially by your webserver configuration, you might need to modify the server configuration to ensure that /.well-known/cf-2fa-verify.txt is accessible.
Option 2: Add a Meta tag to your homepage.
In the header of your homepage for 5 of your active domains (or all your active domains, if you have fewer than 5), add the following before the closing HTML </head> tag:
<meta name="cf-2fa-verify" value="S6TnbBap4SoiS9NcL4K9" />
Verify that you can see this meta tag in your homepage. For security reasons, this must be on the homepage at the root of your domain.
NOTE: If you have a Cloudflare Pages implementation, you can add the above meta tag or file to your Github repo. It will then be deployed to Pages automatically.
After Completion
After you've added this token, reply to this case letting us know on which zones you've added the txt file or meta tag, and we'll be able to proceed.
We appreciate your understanding. Thank you for being part of Cloudflare.

Best Regards,
Luis Pedroza | Technical Support Engineer

aabbOP•5/20/25, 5:42 PM

这是什么意思我该如何操作

aabbOP•5/20/25, 5:47 PM

@Hard@Work 我该我还去做

Aaabb @Hard@Work 我该我还去做

Hard@Work•5/20/25, 5:54 PM

Yeah, you need to follow their instructions so they can help you along

aabbOP•5/20/25, 6:06 PM

可是我该如何做呢，我不会

aabbOP•5/21/25, 8:01 AM

有信任域名

aabbOP•5/21/25, 8:01 AM

第一步我该如何去做

Cayter•5/24/25, 5:45 AM

how have ppl been developing with workers for platforms locally? By connecting to the remote?

CCayter how have ppl been developing with workers for platforms locally? By connecting t...

darkpool•5/24/25, 3:45 PM

yeah or you can use wrangler@dispatch-namespaces-dev

Ddarkpool yeah or you can use wrangler@dispatch-namespaces-dev

Cayter•5/24/25, 3:52 PM

Thx

is dispatch-namespace-dev stable enough?

CCayter Thx is dispatch-namespace-dev stable enough?

darkpool•5/24/25, 3:55 PM

wym by stable?

Original message was deleted

darkpool•5/31/25, 10:58 PM

you can probably automate a lot by using rest api to download worker scripts and upload them as user workers to a dispatch namespace

Original message was deleted

Acе•6/1/25, 2:59 PM

Yeah you will need to upload them as new workers under the dispatch namespace. I’m sure Cloudflare could technically migrate them for you but unless you’re a huge client they won’t bother.

Owl Reddy•6/2/25, 4:03 AM

Does Workers for platforms also increase limits for DBs, Queues, KVs and so on? or is it just for workers?

OOwl Reddy Does Workers for platforms also increase limits for DBs, Queues, KVs and so on? ...

darkpool•6/2/25, 5:45 PM

No. it only increases # of scripts, #of requests, and cpu time https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/platform/pricing/

Benro•6/2/25, 8:55 PM

Hey there!

Can i not access version history/prev deployments of a worker/script deployed to a dispatch-namespace in workers for platform? I do not see any versioning APIs, nor cannot access via UI.

Ddarkpool No. it only increases # of scripts, #of requests, and cpu time https://developer...

Rafflesia•6/4/25, 2:12 AM

this is so well priced I'm almost wondering what the catch is

or maybe I'm just too used to AWS..

RRafflesia this is so well priced I'm almost wondering what the catch is or maybe I'm jus...

Unsmart•6/4/25, 2:28 AM

No catch really but you do want to limit script usage as that can add up if you let users create 100s of tiny scripts. Gotta like mash all em up to one bigger script on the upload side so u save

Rafflesia•6/4/25, 2:30 AM

Rafflesia•6/4/25, 2:36 AM

so to start deploying scripts I can literally just send a PUT to

https://api.cloudflare.com/client/v4/accounts/${process.env.ACCOUNT}/workers/scripts/${"worker-name"}/content

https://api.cloudflare.com/client/v4/accounts/${process.env.ACCOUNT}/workers/scripts/${"worker-name"}/content

Rafflesia•6/4/25, 2:39 AM

or does that only work for "non platform" workers

Rafflesia•6/4/25, 2:41 AM

oh its

https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/dispatch/namespaces/$DISPATCH_NAMESPACE/scripts/$SCRIPT_NAME/content

https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/dispatch/namespaces/$DISPATCH_NAMESPACE/scripts/$SCRIPT_NAME/content

instead

Rafflesia•6/4/25, 2:44 AM

does that also create the worker or does it only work if the worker already exists though

RRafflesia does that also create the worker or does it only work if the worker already exis...

darkpool•6/4/25, 2:19 PM

for uploading entire user worker use https://developers.cloudflare.com/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/

which accepts multi part form data so modules, assets, bindings, etc.

PUT script content is just for updating the JS.

Rafflesia•6/4/25, 5:00 PM

Gotcha

christianklotz•6/5/25, 8:55 AM

Can user workers define their own durable objects, e.g.

class UserDurableObject extends DurableObject<Env>

class UserDurableObject extends DurableObject<Env>

?

For instance, what if I wanted a user worker to receive emails. A standard worker would define an

send_email

send_email

binding. What would a secure setup look like where the email goes through the dispatch worker, and for any user worker supporting email, it would pass it on to be handled by the user worker?

Cchristianklotz Can user workers define their own durable objects, e.g. `class UserDurableObject...

darkpool•6/5/25, 2:39 PM

not sure about DO support since I have not tested it but if you want to pass params from dispatch to user worker you can do it via RPC. User workers can also have bindings to other (non-user) workers so if you had a tools worker with sendEmail method, your user worker could bind to it.

darkpool•6/5/25, 2:40 PM

I'm waiting on workflows support. I was recently told that it should work with WPF but they need to fix something so I assume DO will work too but have not tested it yet.

Ddarkpool not sure about DO support since I have not tested it but if you want to pass par...

christianklotz•6/5/25, 2:50 PM

Thank you! I saw the RPC stuff too. The bottom line is that user workers then always would have to be slightly different than 'regular' workers? I'm still trying to wrap my head around how user workers would have to be written differently.

Ddarkpool I'm waiting on workflows support. I was recently told that it should work with W...

christianklotz•6/5/25, 2:51 PM

Oh, I thought workflows were working on WfP?

Cchristianklotz Thank you! I saw the RPC stuff too. The bottom line is that user workers then al...

darkpool•6/5/25, 2:58 PM

Np. It took me a while to wrap my head around it too. Basically the only difference is how they're invoked. So a regular worker can't RPC a user worker, only a dispatch worker can. However, a user worker can RPC a regular worker directly. The docs dont show this but RPC does work

Cchristianklotz Oh, I thought workflows were working on WfP?

darkpool•6/5/25, 2:59 PM

not yet: workflowsI can't even get the [example](https://

demotime•6/5/25, 3:11 PM

hi all. I was trying to get workers for platforms working, but following the tutorial I couldn't get localdev setup. Does that tutorial still work?
Couldn't find

wrangler dev

wrangler dev

session for "customer-worker-1" in namespace "test" to proxy to

here's the wrangler config for the user-worker:

demotime•6/5/25, 3:11 PM

obviously there's a linter error there (why I screenshotted) - but that is what the tutorial says to do

demotime•6/5/25, 8:02 PM

Your Worker has access to the following bindings:

Durable Objects:
- MAIN_RUN_DO: MainRunObject
KV Namespaces:
- SEND_PROTECT: e5010ba5c178462a8ca7f227d7efa494 [simulated locally]
Dispatch Namespaces:
- DISPATCH_NAMESPACE: test [connected to remote resource]