PostgreSQL service Data tab cannot open connection due to Railway internal server error
okarmazin
PROOP

a year ago

PostgreSQL database content cannot be viewed, tab stuck in an infinite loop at "Database Connection" step.

This is what I see in the browser console:

POST https://backboard.railway.app/graphql/internal?q=getSQLTableNames
{
	"operationName": "getSQLTableNames",
	"query": "query getSQLTableNames($environmentId: String!, $pluginId: String, $serviceId: String, $databaseType: String!) {\n  sqlTableNames(\n    environmentId: $environmentId\n    pluginId: $pluginId\n    serviceId: $serviceId\n    databaseType: $databaseType\n  )\n}",
	"variables": {
		"databaseType": "postgres",
		"directory": null,
		"drive": null,
		"environmentId": "d7596a57-81b2-43e2-9705-4a36b9de0d64",
		"serviceId": "9dcc412f-5401-4c0e-b3bd-97e457424ea4"
	}
}
{
	"errors": [
		{
			"message": "Invalid URL",
			"locations": [
				{
					"line": 2,
					"column": 3
				}
			],
			"path": [
				"sqlTableNames"
			],
			"extensions": {
				"code": "INTERNAL_SERVER_ERROR"
			},
			"traceId": "5804774215718448936"
		}
	],
	"data": null
}
Solved

3 Replies

okarmazin
PROOP

a year ago

Found some old thread about this happening when the service has no public proxy. So I added TCP proxy to the service, error message now reads `"Connection terminated unexpectedly"` and otherwise remains identical

brody
EMPLOYEE

a year ago

Hello, After adding a TCP you need to redeploy, have you tried that?

Status changed to Awaiting User Response Railway • over 1 year ago

okarmazin
PROOP

a year ago

Oh yeah, that did it, thanks! Please mark as solved.

With this new info in mind, here are some suggestions for improvement:
Data tab: The Data tab displayed no errors, just was stuck. The UI had only green checks, which led me to believe project configuration was correct, when it wasn't.
- Data tab should detect missing TCP proxy and instruct the user to set it up.
- Data tab could give a heads up after its HTTP calls repeatedly error out

Settings tab: There is no indication that a service needs to be redeployed after the proxy is added.

  • After adding the proxy, Railway should prompt user to redeploy, like with other changes. Since I am so used to this redeployment requirement being telegraphed in a consistent manner whenever service settings change, I didn't think of redeploying - I believed Railway would have prompted me.

  • https://docs.railway.com/guides/public-networking#tcp-proxying The docs say nothing about redeployment. I did indeed read through the TCP proxy documentation. Since no such requirement was listed in the docs, I didn't think of it.

heart2

Status changed to Awaiting Railway Response Railway • over 1 year ago

Status changed to Solved brody • over 1 year ago

Loading...