Could not create remote preview session on your account
Hi, I'm using honojs and Cloudflare workers and I got this issue when I ran "wrangler dev --remote". It was working yesterday and now its not, I haven't changed anything. Can any one help please?
37 Replies
can you provide more info?
are you getting an error? if so, what?
if you aren't, what do you see?
what's your account id?
The error is "Could not create remote preview session on your account"
my account ID 456951ed65894172e1a74c3fbda9a815
Im just trying to run the server and im getting this error.
I'm experiencing a similar issue. Just started today. I can't tell if I broke something ornot. Previously I would experience the "Could not create remote preview session on your account" issue intermittently but today it's constant.
@ArticBlade in the past removing items that don't work with --remote (like queues) would fix this but I'm now running into this when I have no queues in my project.
Is there some local state that could be blown away that might reset things and fix this? Perhaps in .wrangler/registry ?
My code has no changes yet this happened which leads me to believe it's on cloudflare side. Maybe wrangler requires a different way to communicate or something now.
This just started working for me again.
Yea same so it was indeed a cloudflare issue.
I'm also receiving "Could not create remote preview session on your account" right now. Zero code changes on my end.
I first encountered it a few days ago. Then yesterday it had fixed itself. But now, today, it's erroring again.
I get this whenever I run my project and turn off local mode with the
L key.Exact same as above, presently getting the error:
Could not create remote preview session on your accountaccount id?
Is it a private thing or can I send it here?
could someone also please share debug logs (
WRANGLER_LOG=debug WRANGLER_LOG_SANITIZE=false) - remove your auth token and email me walshy@
you can send here, you can also do /link-account and i can grab it that wayfancy, uno momento plz
ty
I just linked mine too
Where does this go sorry? Doesn't seem to be cmd params
WRANGLER_LOG=debug WRANGLER_LOG_SANITIZE=false wrangler dev --remote would be the full commandAh! I was close lol
mmm, Powershell doesn't like that
hoping this linkedin post is right https://www.linkedin.com/pulse/how-set-environment-variables-using-powershell-tutorialspoint-hkcsc
try
Discount Facebook for the win; we have logs
oh you're going to love this
Getting a log file for you now, but I'll give you a hint: it starts with 4 and ends with 4 🕵️
Hmm
Would this be a cause?
Oh I have a theory..
nah that should be fine
Love a good theory, let's hear it!
Ok looks like there's a bug in something new we're rolling out
if you enable
workers_dev = true it should fix it for nowAll good, I tested in prod like a true dev should and it was fine; hopefully it will be fixed globally next time I need to make a change. Thanks for looking into it 🫡
Let me know if I should also test it and send you my results
You should be good, can do this for now as workaround
Put up PR to fix, hopefully will roll out tomorrow
Great, that means you found and fixed the root cause in your system's code?
yep
Awesome, that's what I love to hear 🙂
Out of curiosity, did it affect many people or were we some obscurely small subset for a particular reason?
it impacts only those who are using workers.dev for the preview (meaning, no routes attached) and have no Workers published on the workers.dev
So, small subset
Got it, so basically just those of us who are following the intro guide for setting up a small project (as is the case for me— I'm using it to view and curate some D1 database values but not actually put them on the public web)— but not yet deployed it.
No dice with or without
workers_dev it would seem :/
Ah, enabling it in the dashboard as well as the config fixed it, for nowFix will roll out today