🐛 BUG: wrangler tail does not work of worker is deployed with Custom domain routing
See original GitHub issueWhat version of Wrangler
are you using?
2.0.22
What operating system are you using?
Mac
Describe the Bug
Wrangler tail does not work if it is deployed to custom domain route. I have console.log('message')
statement in my workers code. Upon request it does not get printed to wrangler tail
console. Neither it gets loged in Workers UI ) Workers -> Services-> Worker-> Logs-> real-time Logs).
My wrangler.toml cofig (scenarion 1):
routes = [{pattern="subdomain.domain.com", custom_domain=true}]
If only I change my wrangler.toml to (scenario 2):
routes = [{pattern = "domain.com/path/", zone_id = "<zoneid>"}]
# routes = [{pattern="subdomain.domain.com", custom_domain=true}]
Things go back to normal.
If I activate buth standard route and custom domain (scenario 3):
routes = [
{pattern="subdomain.domain.com", custom_domain=true},
{pattern = "domain.com/path/", zone_id = "<zoneid>"}
]
ant hit the custom domain, logs are streamed in UI and terminal correctly. Meaning only custom domain is used for routing (scenario 1) logging gets malfunctioned.
It obvious that it’s not a wrangler bug, but a platform bug. But maybe you can escalate it from here.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top GitHub Comments
Linked this issue to internal ticket, thank you for the additional context! 😄
@kevjin
What Cloudflare team do you mean? (both of us are on the CF Workers DevProd team)
Are you on the latest version of Wrangler?
Can you provide a minimal reproduction (Wrangler configuration mostly)