gnuumer Posts - Answer Overflow

gnuumer

Posts Comments

RRailway

•Created by gnuumer on 7/1/2024 in #✋｜help

Issue with Deployment not going live

15 replies

RRailway

•Created by gnuumer on 7/4/2023 in #✋｜help

Why does not attached GitHub account provide enough data?

I have been using Railway extensively for months under a team plan, where I am the lead developer. Now today I cannot put new deployments there anymore since I am not "verified". How come? Please fix this ASAP.

38 replies

RRailway

•Created by gnuumer on 5/13/2023 in #✋｜help

The forced restarting issue

Hello, my Railway deployment has an issue that it redeploys forcibly even though the deployment is set to Never restart, branch automatic triggers are off, and the codebase is stable (there are no errors at all). Had this problem previously. If anyone here knows how to fix it quicker than contacting the Railway team, I'd be grateful. Thanks!

9 replies

RRailway

•Created by gnuumer on 5/4/2023 in #✋｜help

Issue with Postgres on deployment. ECONNREFUSED

Hello, I have an issue that the railway service seems to not connect to the Postgre database even though the DATABASE_URL env variable passed to the program is all correct in correct order as well, so I am suspecting something wrong with my railway setup. The full error log:

> monitor@1.0.0 start
> node ./app/app.js
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 12:09:31 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 12:09:32 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
[MoralisService::cachePrices] prices cached
[MoralisService::cachePrices] prices cached
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5432
}

> monitor@1.0.0 start
> node ./app/app.js
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 12:09:31 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 12:09:32 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
[MoralisService::cachePrices] prices cached
[MoralisService::cachePrices] prices cached
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5432
}

It might be useful to know that the Postgre database server (also deployed in Railway) says that its running on 0.0.0.0 and port 5432. thanks for all help! Project id: 578ca578-fb97-4683-b8ef-2c59b4a09608

383 replies

RRailway

•Created by gnuumer on 5/4/2023 in #✋｜help

Issue with Postgres on deployment

Hello, My node.js backend for a python-based bot is crashing on deployment because of an error connecting to the Postgres database. The DB is in the same service stack. The application uss only the DATABASE_URL with all of the correct parameters pasted from what Railway tells me, so I do not understand why a localhost ip is even there. The full error log is as follows:

npm WARN config production Use `--omit=dev` instead.
> monitor@1.0.0 start
> node ./app/app.js
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 11:39:22 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 11:39:23 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5432
}

npm WARN config production Use `--omit=dev` instead.
> monitor@1.0.0 start
> node ./app/app.js
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 11:39:22 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Thu, 04 May 2023 11:39:23 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1155:14
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5432
}

project id: 578ca578-fb97-4683-b8ef-2c59b4a09608 I also get the notification "Looks like your app is listening on 127.0.0.1. You may need to listen on 0.0.0.0 instead." I read through that documentation intensively but being new to Railway I do not know how to actually have the program listen to that, since it is a mystery for me.

3 replies

Gaming

Programming