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:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 3
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 3
Seems like there is an issue with the initial handshake, which might be a problem with the proxy?
4 Replies
Percy
Percy10mo ago
Project ID: 82bf36ca-fd00-4567-9aa9-5f90227d2f00
lukasgjetting
lukasgjetting10mo ago
82bf36ca-fd00-4567-9aa9-5f90227d2f00
Brody
Brody10mo ago
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?
char8
char810mo ago
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
Want results from more Discord servers?
Add your server