You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Better error for connect/shell on connection failure #980
EDIT I realized it was due to a connectivity issue with my VPN. Ideally the CLI would return a more helpful error in this situation. I've updated the title accordingly
I've encountered an issue where the connect and shell commands immediately error
❯ pscale connect load_testing main
Secure connection to database load_testing and branch main is established!.
Local address to connect your application: 127.0.0.1:3306 (press ctrl-c to quit)
Error: unimplemented: unary response has zero messages
❯ pscale shell load_testing main
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1:54288' (61)
Error: unimplemented: unary response has zero messages
I can see the database so I don't think it's an auth issue
❯ pscale database show load_testing
NAME CREATED AT UPDATED AT NOTES
-------------- -------------- -------------- -------
load_testing 23 hours ago 23 hours ago
Hi @cooperbenson-qz, I'd like to take a stab at this. The plan is to detect proxy connectivity errors in connect.go and shell.go and wrap them with actionable guidance (network/VPN/firewall hints) instead of surfacing the raw "unimplemented: unary response has zero messages". Does that approach work?
Activity
[-]pscale connect/shell failure[/-][+]Better error for connect/shell on connection failure[/+]clanzhang commentedon Jul 21, 2026
Hi @cooperbenson-qz, I'd like to take a stab at this. The plan is to detect proxy connectivity errors in connect.go and shell.go and wrap them with actionable guidance (network/VPN/firewall hints) instead of surfacing the raw "unimplemented: unary response has zero messages". Does that approach work?