11 days ago
There is a bug when creating a new environment based on an existing environment with databases in it, the postgres user password was not synced.
I was able to find a workaround following the support ticket here: https://station.railway.com/questions/web-service-crashing-with-password-auth-e526456d. I understand this is not the same issue, but the workaround there helped.
But I'm puzzled to see why it was closed, as the solution there is not a fix but just a workaround that users can manually hack to bypass the issue. Having the postgres user and PGPASSWORD out of sync seems like something that should be handled in the postgres service.
To clarify, I'm not looking to fix anything, it is working for me now, but to report a bug, (that hopefully would be closed once it is fixed :))
3 Replies
11 days ago
When duplicating an environment, new credential variables are generated for the database service in the new environment, but the database volume is also duplicated with the original credentials baked in, which causes the mismatch you observed. This is a known limitation of the environment duplication flow, and your report is appreciated.
Status changed to Awaiting User Response Railway • 11 days ago
Status changed to Solved Railway • 11 days ago
Railway
When duplicating an environment, new credential variables are generated for the database service in the new environment, but the database volume is also duplicated with the original credentials baked in, which causes the mismatch you observed. This is a known limitation of the environment duplication flow, and your report is appreciated.
11 days ago
It's now more confusing to me the fact that this is known bug but not mentioned when duplicating an environment. And now this issue is marked "solved"? But other developers would still hit the same issue, and spend hours like me trying to figure it out, to find an unrelated issue in the help section that has a workaround, is this the correct way to use Railway?
Status changed to Awaiting Railway Response Railway • 11 days ago
11 days ago
The bot is wrong here, the volume is not duplicated, but new credentials are generated.
In the thread you linked, the user was in thathat situation because they missconfigured something on their end.
Status changed to Awaiting User Response Railway • 11 days ago
Status changed to Open Railway • 11 days ago