Fix SQL Server Ngrok Disconnect
Budget: $10 – $30 USD
I’m running Microsoft SQL Server on a Windows workstation and exposing it over the internet with an ngrok TCP tunnel. The tunnel establishes, the initial ack completes, but the moment the SQL/TLS handshake should finish the session drops and the client is kicked off. Local connections work flawlessly, so the issue lives somewhere between ngrok and SQL Server’s network layer.
The goal is simple: identify the precise reason the handshake fails and apply the configuration change—whether that’s an ngrok flag, a SQL Server protocol tweak, or a firewall adjustment—so remote clients can maintain a stable connection through the tunnel.
If you’re comfortable inspecting ngrok traffic, reading Wireshark captures, and fine-tuning SQL Server Configuration Manager on Windows, you’ll be right at home here.
Deliverables
• A reliable remote connection to my SQL Server instance via the ngrok TCP tunnel, validated from SQL Server Management Studio.
• A concise write-up of the root cause and the fix so I can replicate it on other machines.
I can provide a screen-sharing access for live debugging and am ready to start as soon as you are.
The goal is simple: identify the precise reason the handshake fails and apply the configuration change—whether that’s an ngrok flag, a SQL Server protocol tweak, or a firewall adjustment—so remote clients can maintain a stable connection through the tunnel.
If you’re comfortable inspecting ngrok traffic, reading Wireshark captures, and fine-tuning SQL Server Configuration Manager on Windows, you’ll be right at home here.
Deliverables
• A reliable remote connection to my SQL Server instance via the ngrok TCP tunnel, validated from SQL Server Management Studio.
• A concise write-up of the root cause and the fix so I can replicate it on other machines.
I can provide a screen-sharing access for live debugging and am ready to start as soon as you are.