wrangler.toml configuration file to customize the development and deployment setup for your Worker project and other Developer Platform …
docker run -p 8888:8080 since the default port is 8080...i don't know if this causes issues with Cloudflared-p 8080:8080 would be listening on all IPs anyway) and point cloudflared to that--network host and then localhost will magically work. (This isn't recommended)not entitled: the use of field cf.bot_management.js_detection.passed is not allowed, a Bot Management plan is required when trying to use the cf.bot_management.js_detection.passed field in WAF rules even though the documentation says I can.
/etc/cloudflared/config.yml and removed the part of specifying the config location on the start command ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:8888: connect: connection refused"docker run -p 8888:8080-p 8080:8080--network hostERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 172.17.0.3:8888ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshakehttp://container-ip:8080not entitled: the use of field cf.bot_management.js_detection.passed is not allowed, a Bot Management plan is requiredcf.bot_management.js_detection.passed volumes:
- ${PWD}/tunnel/config.local.yml:/config.yml/etc/cloudflared/config.yml