failing all deploys In addition to deploys that worked previously
Anonymous
TRIALOP

2 years ago

i dont know what is happening

15 Replies

Anonymous
TRIALOP

2 years ago

95669f54-1e79-485f-9b8b-064f51176fda/service/45a3906f-2d3a-4925-bdb2-bea513d407df


brody
EMPLOYEE

2 years ago

we won't know what's happening either, unless you tell us 🙂

please provide your build and deploy logs


Anonymous
TRIALOP

2 years ago

here it is, the deploy logs are empty

1218236905154547783
1218236910191902781


brody
EMPLOYEE

2 years ago

would you happen to be using puppeteer?


Anonymous
TRIALOP

2 years ago

I don't think so, I've been using it without problems for quite some time


brody
EMPLOYEE

2 years ago

please check


Anonymous
TRIALOP

2 years ago

Deleting puppeteer?


brody
EMPLOYEE

2 years ago

would you happen to be using puppeteer? (Y/N)


Anonymous
TRIALOP

2 years ago

I've been using Railway with Puppetear for a year without any problem, you had already helped me upload the program and you had had the same doubt and you had already discarded it, at the time the problem was that I was using Docker badly


brody
EMPLOYEE

2 years ago

For that, I would highly recommend using the browserless template instead of installing chrome into the container.

https://railway.app/template/browserless

here is an example repository on how you would use the browserless template with puppeteer -

https://github.com/brody192/puppeteer-example/tree/main

Please read the README for instructions.


Anonymous
TRIALOP

2 years ago

Hi @Brody, I hope you had a good weekend, that's not the problem, I can't even redeploy an implementation that was already working well, but now it says that the deployment is exhausted, I go back to the deploys from months ago of both the react app and the node app and neither works


Anonymous
TRIALOP

2 years ago

If, with that in mind, you still think I should do that, I'll get to work


brody
EMPLOYEE

2 years ago

I do strongly believe you should switch to browserless, you and another user had reported builds hanging up and timing out at the downloading chrome stage (that's done during npm ci) same exact issue as them and switching to browserless worked a treat for them, additional benefits would be that even if the build didn't time out, building your app without having to download chrome or any of the needed dependencies should by all means significantly cut down on your build and deploys times because the build isn't downloading and installing as much and the published image wont be nearly as big!!


Anonymous
TRIALOP

2 years ago

ohhh, okay!, thanks you very much for the documentation and patience hahah greetings!


brody
EMPLOYEE

2 years ago

happy to help!


Loading...