cheveo
PROOP
a year ago
I always get this log message on my deploy logs. It worked for postgres and redis fine for about a week.
Can't reach database server at postgres.railway.internal:5432
17 Replies
a year ago
you are still on the legacy runtime, please switch to the v2 runtime
a year ago
from within the service settings
this is only required for the backend service? The dbs will have no option for migrating to v2?
a year ago
they are already on v2
a year ago
please use reference variables for redis -
a year ago
awsome
a year ago
no problem!
a year ago
sounds good, you too!