🐛 BUG: Unable to run wrangler dev since version 3.19.0

TL;DR

Since version 3.19.0 of wrangler was released we're no longer able to run wrangler dev --remote.

Steps

1. Since version 3.19.0 of wrangler was released we're no longer able to run wrangler dev --remote. It runs, but as soon as a page is viewed the following error is thrown:
2. [petebacondarwin (contributor)]: Underscores in worker names break TLS hostname verification (test_worker.subdomain.workers.dev fails the check), which breaks wrangler dev --remote and Miniflare fetches. Rename the worker to remove the underscore: do it in the Cloudflare dashboard (Workers -> Manage -> Rename Worker), not by renaming in wrangler.toml, which would orphan the old worker. zehawki confirmed the dashboard rename fixed it with no data loss.

When to use

You are seeing this: It runs, but as soon as a page is viewed the following error is thrown: Use this skill when you run into "🐛 BUG: Unable to run wrangler dev since version 3.19.0".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 3.19.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:cloudflare/workers-sdk#4921 (https://github.com/cloudflare/workers-sdk/issues/4921), the reporter ran into this: Since version 3.19.0 of wrangler was released we're no longer able to run wrangler dev --remote. It runs, but as soon as a page is viewed the following error is thrown: The verified resolution: [petebacondarwin (contributor)]: Underscores in worker names break TLS hostname verification (test_worker.subdomain.workers.dev fails the check), which breaks wrangler dev --remote and Miniflare fetches. Rename the worker to remove the underscore: do it in the Cloudflare dashboard (Workers -> Manage -> Rename Worker), not by renaming in wrangler.toml, which would orphan the old worker. zehawki confirmed the dashboard rename fixed it with no data loss.