a year ago
I redeployed my supertokens-core service and it caused an error with Postgres likely because the Docker image was a new version, so I rolled back to the build that was working today, and now it is no longer working.
The logs say it's connected to the Postgres, but now when I make an API through my nodejs service it isn't responding.
3 Replies
a year ago
The supertokens-core service is only available through private networking which is how I had it earlier today before the error. I'm seeing the error etaddrinfo ENOTFOUND MY_RAILWAY_SERVICE_NAME.railway.internal . MY_RAILWAY_SERVICE_NAME is the actual name by the way I just censored it. It seems like it isn't resolving like normal. I'm seeing this log through railway link
a year ago
When I see the log outside of railway link it says it's a:
ConnectTimeoutError: Connect Timeout Error code: 'UND_ERR_CONNECT_TIMEOUT'
a year ago
I emulated my rollback by finding the docker image available at the time of my working build, and used that to rebuild a fresh service instead of relying on the rollback.
Status changed to Solved brody • over 1 year ago