RAILWAY_TCP_PROXY_DOMAIN and RAILWAY_TCP_PROXY_PORT are empty
I noticed this morning, in my Postgres database PGPORT is set ${{RAILWAY_TCP_PROXY_PORT}} but it's empty. And PGHOST is set to ${{RAILWAY_TCP_PROXY_DOMAIN}} but it's also empty. Otherwise all other variables are in tact.
What could have gone wrong? Is that Railway issue?
7 Replies
Project ID:
f2418602-94ee-49e8-920a-75ca8fa7c054f2418602-94ee-49e8-920a-75ca8fa7c054
Now I created another Postgres instance in the same project and it's fine. But I still need to know what happened to the old one and get access.
was that database deployed from a template?
Thanks for reply, we just had conversation in the forum, so all good:)
But to answer the question this was Umami temple.
Do you generally recommend Docker images vs. GitHub repos?
yes I do
Hey @edgaras ! I'm having the same issue. Would you mind telling me how you solved it?
@Brody This is also happening in Chatwoot template (which I saw you created it) - any hint? I'd like to connect to that Postgres db
Please checkout the overview for the Chatswoot template, it has instructions