i followed the example here:
https://github.com/brody192/puppeteer-example

basically just replaced puppeteer.launch with connect, but seems to have issues

i had it running successfully with headless locally, but tried to convert to browserless to make it workable with railway, but getting this 404 error

i tried running your example @Brody and having the same exact error "Unexpected server response: 404" on the puppeteer.connect call, using this simple example:

```const puppeteer = require('puppeteer');
const path = require('path');

var screenshotsDir = './temp';

async function run() {
const browser = await puppeteer.connect({ browserWSEndpoint: process.env.BROWSERWSENDPOINT }); // <---- crash here with "404" error
const page = await browser.newPage();
await page.goto("https://example.com/");
await page.screenshot({ path: path.join(screenshotsDir, 'screenshot.png') });
await browser.close();
}

run().catch(console.error);```

yep I am aware of the issue and will be fixing it when I'm back from PTO

opps sorry to bother didnt know u were on PTO, when u get back?

this Friday, so I should be fixed saturday at the minimum

great thank u, enjoy the rest of your pto

thank you!

@eddie - template has been fixed, please hard refresh your browser before you deploy the template again

i am still getting 404, what dou mean by hard refresh? i tried redeploying

i tried redeploying the Browserless app, is that what u mean?

you need to redeploy the template

not your pre existing deployment

like create from scratch?

ah okay gotcha

correct, delete that and deploy the template again

and a hard refresh is a key combo that refreshes the page without cache

do i do v2 or v1?

https://github.com/railwayapp-templates/browserless-v2

up to you, v2 dropped support for selenium iirc

thank u it worked! everything is good now <:thumbs:1235596472112644288>
appreciate your help

awsome!

i also have this for testing going forward

this is awesome~

dumb question -- how do i expose the railway URL of a project as an env variable? how does it know its own url?

how does browserless expose its own url as env var:
wss://[browserless-production-823f.up.railway.app](browserless-production-823f.up.railway.app)

not a dumb question, it uses the reference variable RAILWAY_PUBLIC_DOMAIN

you can view the raw editor to see how it's all pieced together.

docs here -

perfect thank you!

great service, as always. loyal customer since 2021 <:salute:1137099685417451530>

please close this thread, issue resolved

sounds good! happy to help 🙂