a year ago
Im trying to deploy with railway and I have like 3 hours until I need to send this as my final project. I kinda have it in a good state but I need to host it. this are the logs
ass an extra I can say that I was able to host my server on docker and I already tried uninstalling and installing everything, moving dependencies to devdepencencies and other things. all I can say is that this debugging sucks with how broad is killed as an error pls help
npm
WARN
config
production Use --omit=dev instead.
Killed
container event container died
npm
WARN
config
production Use --omit=dev instead.
INFO: MONGO CONNECTED
INFO: environment {"DB_LINK":"********","GOOGLE_CLIENT":"********","GOOGLE_EMAIL":"********","GOOGLE_ID":"********" and so on (this are my env variables I don't show them but they are correct.)
INFO: environment: test
INFO: clusterIsPrimary: true
INFO: cpuCores: 32
INFO: Primary Id: 15
Killed
container event container died
npm
WARN
config
production Use --omit=dev instead.
> backendproject-master@1.0.0 start
11 Replies
a year ago
if anyone can help I can join discord or whatever
a year ago
Please send your build and deployment logs -
a year ago
Please send your build and deployment logs -
I can't use that link and also don't want to show env keys. it doesn't let me show the deply logs will take screenshots
a year ago
Please send your build and deployment logs -
a year ago
Please send your build and deployment logs -
https://bookmarklets.up.railway.app/log-downloader/ the rest is just image beeing publish for 40 seconds or so
Attachments
a year ago
I won't be able to help with these screenshots, please use the bookmarklet, you are welcome to edit out the sensitive information from the logs before you send it.
a year ago
please tell me how to use it, im in operagx
a year ago
Follow the 3 steps. Though operagx is challenging, use chrome.
thanks for the help
Attachments
a year ago
Follow the 3 steps. Though operagx is challenging, use chrome.
sorry for the wait I was doing the new deploy without those console.log
a year ago
I'm seeing a Killed message and from my experience that means your app ran out of memory, please upgrade to the Hobby plan and try another deployment.