CD
Cloudflare Developers•4w ago
Samko

wrangler dev --remote - 504 Gateway timeout after 60s

Hello, It is possible that when using wrangler in remote mode there is hard limit of 60s timeout for worker request to process? I have simple hono route that is always timeouting in remote mode but passes in local only mode. I need remote mode for working with browser rendering. 
app.use("/timeout-test", timeout(140000));
app.post("/timeout-test", async (c) => {
  await new Promise((resolve) => setTimeout(resolve, 120000));
  return c.json({ message: "Timeout test" });
});
app.use("/timeout-test", timeout(140000));
app.post("/timeout-test", async (c) => {
  await new Promise((resolve) => setTimeout(resolve, 120000));
  return c.json({ message: "Timeout test" });
});
on wrangler dev --remote: [wrangler:inf] POST /timeout-test 504 Gateway Time-out (62861ms) on wrangler dev: 
{
    "message": "Timeout test"
}
{
    "message": "Timeout test"
}
Any way to fix that ?
1 Reply
Samko
SamkoOP•4w ago
thanks for the tip! I went with locally running chrome instead and using 
const browser = await puppeteer.connect({
      browserWSEndpoint: `ws://127.0.0.1:9222/devtools/browser/fe40e5bd-2d09-4520-9333-031ab8843097`,
    });
const browser = await puppeteer.connect({
      browserWSEndpoint: `ws://127.0.0.1:9222/devtools/browser/fe40e5bd-2d09-4520-9333-031ab8843097`,
    });

Did you find this page helpful?