Unable to connect to newly migrated MySQL service from outside the Railway network
Hi there! I just migrated a legacy MySQL plugin to a service using the migration tool.
My API service can correctly connect to the database using the internal domain (
database.railway.internal).
However, I am unable to connect to the MySQL service from my own machine, using the public domain proxy (roundhouse.proxy.rlwy.net:22516).
I receive the following error:
Seems like there is an issue with the initial handshake, which might be a problem with the proxy?4 Replies
Project ID:
82bf36ca-fd00-4567-9aa9-5f90227d2f0082bf36ca-fd00-4567-9aa9-5f90227d2f00
there is an ongoing issue, but it was my understanding that it was fixed
https://discord.com/channels/713503345364697088/846875565357006878/1195486553246552154
@char8 - seems like theres still an issue with the proxy?
Hi - super apologies about that - it ended up being a very gnarly bug. I managed to clear the route caches early so stuff should've resumed about 50 mins ago. But we've rolled out a proper fix and are going to close out the incident as soon as we've done some more test.s
it was triggered by re-deploys of a service frontend by tcp-proxy, the new routes weren't propagated to all the proxies