Yannick
The value of my read variable is different from that edited.
RAILWAY_ENVIRONMENT can take what value?
I can't find it in the documentation:
https://docs.railway.app/reference/variables#railway-provided-variables
9 replies
Connection refused to local node on port 8546.
Where are you in your investigation?
I placed the environment variables of my service which did not work one of those which worked and it worked.
I placed the environment variables of my working service in one of the non-working ones and it didn't work.
My last manipulation was to deploy four other services in the project as I usually do and the applications respond well.
Why do my other six services remain blocked while when I carry out the same deployments in the same project it succeeds?
20 replies
Connection refused to local node on port 8546.
@Brody @Angelo The reproduced error found that the container did not communicate with the database as if the environment variables were not read.
I actually have a loop in the code which inserts into the database the events it receives at regular intervals.
Building an image launched with Nixpacks (in a local setup) for my monitor works if all the variables are known. An error in the environment variables of the external postgres v15 database causes the same error as in the Railway logs.
The database identifiers are the same as the running services and the database metrics are ok.
20 replies
Bug in the builder that no longer works
A Railway bug prevents the builder from starting for another 7 of my servers via the graphical interface.
Once in my service, I click on the three small dots, those next to 'View Logs', I launch
Redeploy and I obtain logs after 6 minutes which fit into one line:
No build logs found for deployment
Do the elements I provided allow you to resolve the problem?12 replies
Bug in the builder that no longer works
The Railway cli was able to work again to allow the builder to be restarted. The Railway up command had not worked in previous days.
The service is active again, also the problem is propagating among the 9 other servers, the Github cli, Github action, on two of them seems to work. So I'll give you some time to find your bug. For my part I am now able to get around the problem.
Please keep me informed of the progress of the problem.
Here my
Build Logs:
Here my Deploys Logs:
Here my View Logs:
Here my package.json file:12 replies
Websocket no longer listens to events and no error returns.
My websocket sleeps like when a serverless node.js app shuts down after some time of inactivity.
Unlike a serverless, no broken or complaining my websocket which has a KEEP_ALIVE_CHECK_INTERVAL stays in deep sleep.
Do you have an idea ?
6 replies
Questions about automatic deployment with a new PR.
I finally got the deployment with a second PR.
It must surely be a bug.
Also there was a bug when the merge of my pr was done on production (manual branch selection) when there was no main branch deployed, it did not redeploy and it moved to main due to pr branch removal.
Thank you.
7 replies