failing all deploys In addition to deploys that worked previously
i dont know what is happening
Solution:Jump to solution
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 -...
15 Replies
Project ID:
95669f54-1e79-485f-9b8b-064f51176fda95669f54-1e79-485f-9b8b-064f51176fda/service/45a3906f-2d3a-4925-bdb2-bea513d407df
we won't know what's happening either, unless you tell us 🙂
please provide your build and deploy logs https://bookmarklets.up.railway.app/log-downloader/
here it is, the deploy logs are empty
would you happen to be using puppeteer?
I don't think so, I've been using it without problems for quite some time
please check
Deleting puppeteer?
would you happen to be using puppeteer? (Y/N)
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
Solution
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.
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
If, with that in mind, you still think I should do that, I'll get to work
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!!ohhh, okay!, thanks you very much for the documentation and patience hahah greetings!
happy to help!