@warren.strange wrote:
I discovered the source of my runaway CPU and non-functioning warp ingress. My ingress hostname had a subdomain component:
foo.default.acme.com, not foo.acme.com
Which I gather warp doesn’t like. I ran into the same issue running the Cloudflare-warp command line utility. If I trim off the sub domain, it seems to work fine.
Not sure if this qualifies as bug or not - but it might be good to document this.
