71 Replies
Project ID:
5dc852b8-a45d-4fa3-b1e2-f8adb79c85b45dc852b8-a45d-4fa3-b1e2-f8adb79c85b4
has this app successfully built before?
it was running ok for last couple of months
is there any new incident recently?
I think that affects the running application
no incidents reported right now, can i get your build logs please https://bookmarklets.up.railway.app/log-downloader/
node 14 is no longer supported please update to node 16 or 18
There is no active development for this project for last couple of months and running perfectly ok, I found the app crashed after logging the account
what kind of app?
it's a strapi app
gotcha, yeah you would need to use node 16 or 18
node engine set up for the range
just set that to
16ok let's try.will give an update
still failed
build logs again please
I have another instance running for another client, that one is running fine
now its trying to install node 18, please set your
engines.node to 16failed
i think it's not node engine issue
rather railway infrastructure issue
build logs please
railway is not experiencing any infrastructure issues right now, i have seen these errors before
try adding a nixpacks.toml to your project with this in it
In root directory?
if thats where strapi deploys from, yes
failed
do you have a date of when the last build was successful?
it was running successfuly, suddenly it crashed
im sorry but that doesnt quite answer my question
May be last build was 1 month back
what is that commit dated
recently it crashed without any intervention
may be this one almost 7 months ago
Commits on Jul 18, 2023
thats a lot longer than 1 month back
yes those were real dev changes, But I have n't found any commit history in between
2024-02-02 03:58:49.359] debug: ⛔️ Server wasn't able to start properly.
[2024-02-02 03:58:49.360] error: connect ECONNREFUSED 34.127.40.22:7018
Error: connect ECONNREFUSED 34.127.40.22:7018
you got it to build?
when I tried restart the crashed one, it show me the message, I think App could not be connected properly to the expose IP
no For new build it's failed on build stage by docker
we need to get a new build working, so give me a few minutes
i have updated this, please update your local file
could you elaborate?
what do you mean by updating your local file?
update your projects nixpacks.toml file with this
failed again
for future referance, if it fails please go ahead and send me the logs
interesting, okay last ditch effort.
delete your nixpacks.toml file.
add a railway.json to your project with this in it
did you update some packages?
no
please inform to your seniors, I will try later.Thanks
i assure you this isnt an issue with railway
And I am 100% sure, it's railway issue
im sorry but its not
this is a 7 month old project, things break
it seems like the build wants node 18 again, so set
engines.node to 18I will try thanks
npm WARN config production Use
--omit=dev instead.
[email protected] start strapi start[2024-02-02 08:48:59.997] debug: ⛔️ Server wasn't able to start properly. [2024-02-02 08:48:59.999] error: connect ECONNREFUSED 34.127.40.22:7018 Error: connect ECONNREFUSED 34.127.40.22:7018 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) npm WARN config production Use
--omit=dev instead.
[email protected] start strapi start[2024-02-02 08:49:04.292] debug: ⛔️ Server wasn't able to start properly. [2024-02-02 08:49:04.294] error: connect ECONNREFUSED 34.127.40.22:7018 Error: connect ECONNREFUSED 34.127.40.22:7018 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) npm WARN config production Use
--omit=dev instead.
[email protected] start strapi start[2024-02-02 08:49:08.514] debug: ⛔️ Server wasn't able to start properly. [2024-02-02 08:49:08.516] error: connect ECONNREFUSED 34.127.40.22:7018 Error: connect ECONNREFUSED 34.127.40.22:7018 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) npm WARN config production Use
--omit=dev instead.
[email protected] start strapi start[2024-02-02 08:49:12.750] debug: ⛔️ Server wasn't able to start properly. [2024-02-02 08:49:12.752] error: connect ECONNREFUSED 34.127.40.22:7018 build successful but couldn't able to connect remote IP
send your database.js file please
const { parse } = require("pg-connection-string");
module.exports = ({ env }) => {
const { host, port, database, user, password } = parse(env("DATABASE_URL"));
return {
connection: {
client: "postgres",
connection: {
host,
port,
database,
user,
password,
},
debug: false,
},
};
};
send the file please
error: connect ECONNREFUSED 34.127.40.22:7018
connection refused, what might be the reason?
DATABASE_URL=postgresql://postgres:[email protected]:7018/railway
env variable
you are still trying to connect to the legacy database, please send a screenshot of your railway project
got it , it seems structure is changed, 2 varibale availble now , one is DATABASE_PRIVATE_URL, and another one is DATABSE_URL
which one I should connect
on the strapi service set
DATABASE_URL to ${{Postgres.DATABASE_PRIVATE_URL}}Thanks for your time
back online?
yes
awsome
it's all package related inconsistency and node version
yep, no railway issues here
I forgot the recent changes of database update issue , that why it shows me the error of IP related connection refused issue
anyway thanks for your time
yeah thats the shut down database