on the proxy service, you are using public hosts and ports, which will cause the user to incur double egress fees, I suggest using private domain and port reference variables.

@brody great catch, thank you… i'll update accordingly.

Hey @trogdor thanks for sharing this with us. I have deployed a windmill instance, and enabled public networking for the proxy module (caddyfile). even when using http i am getting a "not found" error

any ideas on how to fix? thanks!

Hey, is there any way to spin up a worker with the chromium label so that I can run puppeteer?

https://www.windmill.dev/docs/advanced/browser_automation#puppeteer-bun

1. On Railway, duplicate your "worker" instance.

2. On the duplicated instance, change the WORKER_GROUP variable from "default" to "reports".

3. Assign the "chromium" tag to a job in Windmill.

   It will run on the new worker with the "reports" WORKER_GROUP variable.

@Trogdor this is no longer functional - the proxy returns 502s. I tried a deploying this template fresh and have the same issue

were you ever able to figure out how to use internal hosts and ports on the proxy service?