a year ago
Hi there, i have a problem with all databases that was generated by the PR environment.
I'm using the beta functionality that duplicates all databases from another env and when i tried to access some of the databases, i receive an authentication error.
The railway dashboard also receives an error when tries to connect them.
I recognize that this feature is in beta test. I'm just reporting the error and if its simple to fix, i'd appreciate so much.
Project ID: e60124ce-5bb4-41cb-8517-9606dbe5b9f7
Environment: pr-929 (Environment ID: a3badbef-9764-400e-b70e-c27654ca4475)
17 Replies
Just correcting: Not all databases are like this, I was able to access one of them normally from the beginning.
The railway dashboard probably connects using private network.. my microservices also connects like this. I also tried to connect through by public network.. had no effect
a year ago
data tab connects to the database via the public network
a year ago
service id please?
i copied the environment variables correctly. Internally everything is linked, so I believe it was not a user error.
as everything was duplicated from another environment, theoretically it was supposed to work
a year ago
MONGO_INITDB_ROOT_PASSWORD
as the name suggests, its only used on init for a blank db, once the database has been initialized, the password is now stored in the volume.
but when the pr env got created, the templates generator created a new variable.
data tab now uses the wrong password, and cannot connect.
a year ago
ah looks like as of 30 minutes ago this is fixed (your pr env was created 3 days ago)
for all pr envs with copy volume data enabled, we do not run the generators anymore, so all passwords in pr envs will be the same as the passwords in the base pr branch
a year ago
maybe close and re-open? not too sure the best practices around that are
a year ago
awsome!
a year ago
!s
Status changed to Solved brody • about 1 year ago