90126b32-7716-4f6e-8326-00312abc6db6

Error using playwright on project

I can not recommend using Browserless enough, using it means you don't have to install Chrome and all of its needed dependencies into your container, and this will significantly speed up both the build and the publishing stage.

Browserless template here - https://railway.app/template/browserless

And here's my little example repo that shows you how to use browserless with playwright - https://github.com/brody192/playwright-example

ok but

but?

where i can find this env

WSENDPOINTPLAYWRIGHT=${{Browserless.WSENDPOINTPLAYWRIGHT}}

this

'WSENDPOINTPLAYWRIGHT"

the template do it?

yes that's provided by the template

okayy

i will try

how i can use this template?

just click on 'Deploy Now'?

i never use template on railway

nope, open your pre-existing project and click the + New button and search for the template

okay

and click deploy?

yes, as long as you follow my instructions

looks good!

and just change like this:

const browser = await playwright.chromium.connect(process.env.WSENDPOINTPLAYWRIGHT);

yep that looks right

you'd also want to remove your custom build command that tries to install chrome

hey brody good night, I ended up leaving home and only returned now

same error using browserless

1223399006709878784

build logs please

1223399426362708119

okay and show me your playwright.chromium code please

1223400643507523744

are you sure you arent calling chromium.launch elsewhere?

yes, have other functions

all i ve changed

but this are the first

your code is still trying to launch chrome

and have the error

Do I have to set up any ENV variables?

this WSENDPOINTPLAYWRIGHT

yes you do, please read the readme

WSENDPOINTPLAYWRIGHT=${{Browserless.WSENDPOINTPLAYWRIGHT}}

this

correct?

yes, that needs to be set on your app's service

but i dont use app service

i will send you my main.js

it is simple bot

1223402986563305503

look

just a cron who will run everyday

instead of typing out the name of the service you use i simply said app as a generic cover, i am talking about the service in the top left of this screenshot

broo

I don't believe it

what?

I went to check the variable and it was missing a point

that would be an issue

I changed it and now it's gone

I'm sorry

how i can pay you?

for this help

theres no need for pay lol

okay

i ve looking for browserless website

i appreciate the offer though ❤️

and i saw the 'pricing'

well now you are self-hosting it, so you only have to pay railway's usage pricing

okay thats right

I don't know if you noticed, but I'm from Brazil so bad English ahaha

nah your english is fine

1223405660352548997

this is common?

to much issues now

is your service not working?

yes

then the logs are normal

are closing the browser

the internet are slow on railway?

i have to change the 'waitforselector'?

look this line 'page.waitForTimeout: page.waitForSelector: page.waitForSelector: Target page, context or browser has been closed'

browserless closes its chromium browser when not in use to save on resources

but it was in 100% use, i didn't understand mt well i'm going to change the codes and test again

each call to chromium.connect would spawn another browser and then it would get closed, if your service works fine, then theres nothing to worry about

my service isn't working it's taking 1/8 of the data

im not sure what "1/8 of the data" means

it is dosent working hahaha

i dont know why the browser are closing

i will put more time between functions

the browser is closing because they did what your code asked them to do

running here on my computer locally it works now online it closes

thats how browserless works

same issues here

i dont know what is going on

beacuse the page are open and the console show this issues: page.waitForTimeout: page.waitForTimeout: page.waitForTimeout: page.waitForTimeout: page.waitForTimeout: page.waitForTimeout: page.waitForTimeout: page.waitForSelector: page.waitForSelector: page.waitForSelector: page.waitForSelector: Target page, context or browser has been closed

at links (/app/pegarlinks_caixa.js:59:24)

at /app/async file:/app/test.js:23:29

i ve put a console.log if page are closed

okay but is that causing your app to not work correctly?

Yes, as it is a site that takes a long time to load there are waitforselector with very long timeouts

how can i change in browserless to stay more on the page?

browserless has it's timeout set at 5 minutes, I can't see you needing more than that