Unable to connect to newly migrated MySQL service from outside the Railway network | Railway | Page 1

hallow coral Jan 12, 2024, 11:43 PM

#

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

Seems like there is an issue with the initial handshake, which might be a problem with the proxy?

hollow narwhalBOT Jan 12, 2024, 11:43 PM

#

Project ID: 82bf36ca-fd00-4567-9aa9-5f90227d2f00

hallow coral Jan 12, 2024, 11:44 PM

#

82bf36ca-fd00-4567-9aa9-5f90227d2f00

scenic swan Jan 12, 2024, 11:50 PM

#

there is an ongoing issue, but it was my understanding that it was fixed
#🚨｜incidents message

#

@radiant umbra - seems like theres still an issue with the proxy?

radiant umbra Jan 13, 2024, 1:10 AM

#

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

#Unable to connect to newly migrated MySQL service from outside the Railway network