Skip to content
Mysql connection
afonsovinagre
OP

2 months ago

MySQL service online, logs show "ready for connections" on port 3306. TCP Proxy (reseau.proxy.rlwy.net:30513) times out from two different networks (home + mobile hotspot), while my API on Railway connects fine to the same URL. DNS resolves (66.33.22.231), google.com:443 works from my PC. Also railway ssh fails with a timeout on ssh.railway.com:22. The Database tab in the dashboard shows an infinite "Attempting to connect" spinner. Project ID: 459eba5b-316c-4e19-99f6-5a8fe58569d3, service ID: f114bb7e-4ae6-44a3-8ce2-2af6cccd999e.

$20 Bounty

8 Replies

Railway
BOT

2 months ago

We haven't found a fault on the Railway side of this. The rest of what's involved is your machine, your network, and the client tooling, and that's where this most likely stalls, so getting to the bottom of it means someone hands-on with a setup like yours.

That's exactly what the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

  • Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
  • Keep it private and close the thread - Nothing becomes public and the thread closes.

Status changed to Awaiting User Response Railway • about 2 months ago


Railway
BOT

2 months ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • about 2 months ago


Try selecting your service, press Cmd/Ctrl + K, and redeploy source image.


0x5b62656e5d

Try selecting your service, press Cmd/Ctrl + K, and redeploy source image.

afonsovinagre
OP

2 months ago

The problem remains the same.


What region is the database deployed in? Also, I’d try using a VPN as well.


0x5b62656e5d

What region is the database deployed in? Also, I’d try using a VPN as well.

afonsovinagre
OP

2 months ago

The database is deployed in Amsterdam. I’ve also already created a new MySQL service, but I’m still having the same connection issues. I also tried using my phone’s hotspot instead of my usual network, but the problem persists.


afonsovinagre
OP

2 months ago

I tried Firefox VPN and it still din´t work.

image.png


4ndrvstudio

2 months ago

Your screenshot appears to show Firefox's built-in VPN. That feature only routes traffic originating inside Firefox; it does not route your external MySQL client or railway ssh. So those two connection tests would still use their original network path with that VPN enabled. Mozilla documents this distinction here: https://support.mozilla.org/en-US/kb/built-in-vpn

I checked TCP connectivity from a separate network at 2026-10-06 04:52 UTC: both reseau.proxy.rlwy.net:30513 and ssh.railway.com:22 accepted connections. I did not authenticate to either service. This establishes that both endpoints were reachable from at least one external network at that time; it does not establish what is blocking your path.

The next useful comparison is with a VPN that routes the whole device, ensuring the MySQL client and terminal are included, then repeat the raw TCP check outside the browser. For example, in Python:

import socket

for host, port in [("reseau.proxy.rlwy.net", 30513), ("ssh.railway.com", 22)]:
    try:
        with socket.create_connection((host, port), timeout=5):
            print(host, port, "TCP OK")
    except OSError as exc:
        print(host, port, type(exc).__name__, str(exc))

Run it once on the normal connection and once with the device tunnel active. If both start working, that narrows the problem to the original outbound path. If both still fail, preserve the results and UTC time for Railway to correlate. Keep the dashboard spinner as a separate observation: a browser VPN test and a native TCP-client test are different paths, and the spinner alone cannot tell us whether the raw TCP proxy is reachable.

This is a targeted diagnostic correction, not a confirmed fix for your machine. AI-assisted analysis; the two TCP checks above were actually performed.


jayubha1121

2 months ago

I believe this is a Railway networking/access-path issue rather than a MySQL service issue.

Here is what I verified:

  • The MySQL service is running normally and its logs show ready for connections on port 3306.
  • My Railway API service can connect to the same MySQL instance successfully through the internal Railway connection URL, so the database itself is reachable and accepting connections.
  • The external TCP Proxy reseau.proxy.rlwy.net:30513 consistently times out.
  • I reproduced the TCP timeout from two independent networks: my home connection and a mobile hotspot, which makes a local firewall/router issue unlikely.
  • DNS resolution works and resolves the proxy hostname to 66.33.22.231.
  • Normal outbound HTTPS connectivity from the same machine works (google.com:443).
  • Railway SSH also times out on ssh.railway.com:22.
  • The Railway Database tab remains stuck indefinitely on Attempting to connect.

This makes the failure appear to be above the MySQL process itself, most likely in the Railway public TCP/edge access path or the dashboard/database access path.

I would not recommend changing MySQL configuration, credentials, or the application's internal connection string, because the internal Railway connection is already working.

Suggested checks:

  1. Verify that the TCP Proxy for the MySQL service is targeting the correct internal port 3306.
  2. Disable/re-enable or recreate the TCP Proxy and test the newly generated *.proxy.rlwy.net: endpoint.
  3. Check whether the newly assigned proxy resolves to the same 66.33.22.x edge range and whether TCP connectivity still times out.
  4. Test the public path directly with a MySQL client using a short connection timeout.
  5. Check Railway's edge/TCP proxy logs for the affected project/service around the failed connections.
  6. Check whether there is an active incident affecting TCP Proxy or SSH access.

Railway's documentation confirms that external MySQL access is provided through a TCP Proxy, while services inside the same Railway environment should use the private connection variables. Railway Docs

Since both the public MySQL TCP connection and Railway SSH are timing out while the deployed API and MySQL remain healthy internally, could Railway please check the public networking/SSH access path for this project?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...