i have problem with deploy

10 months ago

i disconected inside the menu in "source" to switch to my github but it can not recognized there my github to add and image and now i do not know how to come back to make reployment of new version of n8n because i always write in that space "source" that now only appears the place of repository, do not work too, how can i manage? is there any other way to update the versions of n8n in other part of railway? where' how'

thank you for your soon reply

$10 Bounty

8 Replies

Railway
BOT

10 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


idiegea21
HOBBY

10 months ago

Heyy!!

If you disconnected the "Source" and can't re-link your GitHub, you can still update n8n by redeploying manually. Go to your Service > Deployments tab > Deploy from GitHub or Docker, or use the "Upload" option to push your updated code or image. If it's a container app, updating the image/tag manually also works.


treetameyn2520
HOBBY

10 months ago

Hello, I have a problem publishing from the GitHub repository. When I update the repository and publish it, the publishing is canceled and the page cannot be opened.


treetameyn2520

Hello, I have a problem publishing from the GitHub repository. When I update the repository and publish it, the publishing is canceled and the page cannot be opened.

clashing
FREE

10 months ago

What is the error coming? You can see that in the deployment/build logs


clashing
FREE

10 months ago

hulk, what is the actual issue? Isn't your Railway dashboard showing up your repositories?


treetameyn2520
HOBBY

10 months ago

npm warn config production Use --omit=dev instead.

npm error code EUSAGE

npm error

npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.

npm error

npm error Invalid: lock file's express@5.1.0 does not satisfy express@4.21.2

npm error Missing: path@0.12.7 from lock file

npm error Invalid: lock file's accepts@2.0.0 does not satisfy accepts@1.3.8

npm error Missing: array-flatten@1.1.1 from lock file

npm error Invalid: lock file's body-parser@2.2.0 does not satisfy body-parser@1.20.3

npm error Invalid: lock file's content-disposition@1.0.0 does not satisfy content-disposition@0.5.4

npm error Missing: cookie@0.7.1 from lock file

npm error Invalid: lock file's cookie-signature@1.2.2 does not satisfy cookie-signature@1.0.6

npm error Missing: debug@2.6.9 from lock file

npm error Invalid: lock file's finalhandler@2.1.0 does not satisfy finalhandler@1.3.1

npm error Invalid: lock file's fresh@2.0.0 does not satisfy fresh@0.5.2

npm error Invalid: lock file's merge-descriptors@2.0.0 does not satisfy merge-descriptors@1.0.3

npm error Missing: methods@1.1.2 from lock file

npm error Invalid: lock file's path-to-regexp@8.2.0 does not satisfy path-to-regexp@0.1.12

npm error Invalid: lock file's qs@6.14.0 does not satisfy qs@6.13.0

npm error Invalid: lock file's send@1.2.0 does not satisfy send@0.19.0

npm error Invalid: lock file's serve-static@2.2.0 does not satisfy serve-static@1.16.2

npm error Invalid: lock file's statuses@2.0.2 does not satisfy statuses@2.0.1

npm error Invalid: lock file's type-is@2.0.1 does not satisfy type-is@1.6.18

npm error Missing: utils-merge@1.0.1 from lock file


clashing
FREE

10 months ago

Remove the package-lock.json file from your code repository, because there are some mismatches in the package.json & the lock file. Then push the same to Railway. Hopefully, it would remove these errors


clashing

Remove the package-lock.json file from your code repository, because there are some mismatches in the package.json & the lock file. Then push the same to Railway. Hopefully, it would remove these errors

clashing
FREE

10 months ago

Did that helped?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...