https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • b
    that would be a major bug or is it a feature....
  • b
    this is a bug
  • b
    gRPC Allow gRPC connections to your origin server. Learn more. WebSockets Allow WebSockets connections to your origin server. Concurrent connection guidelines for your plan: low. Learn more. This setting was last changed a few seconds ago
  • b
    If I turn off gRPC and WebSockets dash toggles, for my custom domain, CFW quick edit, dev tools crashes
  • s
    Is it possible to use an HTTP proxy server when making outbound fetch calls from a Worker? I have some external services that are IP-restricted, and since CF Worker IPs aren't static I need to proxy it through another server (via tunneling) to make the call.
  • l
    I have done that. I need to fetch from a non-standard https port. Nginx proxy works flawlessly. Not very convenient though, as it introduces more moving parts, that can fail…
  • l
    I am hoping, that Cloudflare will allow fetch requests to non-standard ports someday…
  • s
    Ah, gotcha, so you just made requests directly to the nginx reverse proxy?
  • l
    Yes
  • s
    Thanks, seems like that'll end up being the lightest solution
  • s
    Does that example work for you. I copy it and trying to run it to see it work and it giving me errror
    Copy code
    ✘ [ERROR] Expected ")" but found ":"

    src/index.js:4:23:
      4 │     async fetch(request: Request, env: Env): Promise<Response> {
        │                        ^
        ╵                        )


✘ [ERROR] Expected ")" but found ":"

    src/index.js:4:23:
      4 │     async fetch(request: Request, env: Env): Promise<Response> {
        │                        ^
        ╵                        )
    So before I try anything wanted to see if it worked for your or someone else.
  • w
    looks like you're using JavaScript not TypeScript
  • w
    if you remove the typing, it should work
  • s
    It is javascript. I just recreated it with the typescript option and it doesn't like fetch still.
  • s
    Copy code
    Cannot read properties of undefined (reading 'fetch')
  • w
    what's your full code?
  • s
    I just copied the example as it looked complete.
    Copy code
    import puppeteer from "@cloudflare/puppeteer";

export default {
    async fetch(request: Request, env: Env): Promise<Response> {
        const browser = await puppeteer.launch(env.MYBROWSER);
        const page = await browser.newPage();
        await page.goto("https://example.com");
        const metrics = await page.metrics();
        await browser.close();
        return new Response(JSON.stringify(metrics));
    },
};
  • c
    iirc you're missing node_compat? Or browser isn't set? I got that same error when I was setting this up yesterday, and it was fixed by me copying their wrangler.toml, can't remember if it was node_compat specifically or something else though. If you don't have it set at all though, you should
  • c
    your wrangler.toml should be like:
    Copy code
    name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }
    Make sure you're not trying to test locally as well. If you're on the latest wrangler/wrangler@3, use 
    npx wrangler dev --remote
  • w
    yeah seems like MYBROWSER isn't defined as a browser binding
  • s
    this what I have in wrangler.toml name = "testcf" main = "src/index.ts" compatibility_date = "2023-05-24" node_compat = true workers_dev = true browser = { binding = "MYBROWSER", type = "browser" } Warning on publishing
    Copy code
    ⛅️ wrangler 2.19.0 (update available 3.0.1)
------------------------------------------------------
▲ [WARNING] Processing wrangler.toml configuration:

    - Unexpected fields found in top-level field: "browser"


▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.
    Error when I publish it is 1101. I haven't moved to version 3 of wrangler as the command changed so I need to have a minute to figure it out
  • w
    aww man... you do need 3.0
  • w
    you can use unsafe for now
    Copy code
    toml
[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"
  • s
    I'm planning on moving to 3.0. The create command works doesn't much how I like to layout my directories and in my editors. So I just need to figure out how I want to make it work. The way I do thing now is create git repo or using existing one. Then I would clone it down and then cd to that directory and do the init command it would create everything. Now it create a directory with everything in it. So I just need to do some playing.
  • s
    after work tomorrow I will upgrade to 3.0 and give it another try
  • u
    I write fetch together with tail but tail doesn't work
  • u
    I tried specifying myself in 
    wrangler.toml
    but it won't work either
  • u
    Copy code
    ts
export default <ExportedHandler<Env>> {
    async fetch(req, env, ctx) {
        ...
    },

    async tail(events, env) {
        for (const event of events) {
            if (!(event.event as TraceItemFetchEventInfo).request) continue;
            await env.BUCKET.put(
                '',
                JSON.stringify(event),
                { httpMetadata: { contentType: 'application/json' } }
            );
        }
    },

    async scheduled(event, env, ctx) {
        ...
    }
};
  • n
  • n
1...249324942495...2509Latest