Bug: SSH-tunneled staging/production connections show password error after being idle for a few days

[huynd111]

What happened?

After leaving saved database connections unused for a few days, reopening the connections shows a password/authentication error.

This only happens for staging and production databases connected through an SSH tunnel via AWS EC2.

Local database connections do not have this problem.

At the moment, it looks like the saved SSH/database auth state becomes invalid or is restored incorrectly after the connection has been idle for some time.

SSH setup

• SSH tunnel: Yes
• SSH host: AWS EC2
• Environment affected: staging, production
• Environment not affected: local

Additional notes

• The issue is reproducible on remote DBs accessed over SSH, but not on local DB connections.
• It seems related to reconnecting/restoring saved SSH-based connections after being idle for a while.
• Please let me know if you want logs or a sanitized connection setup example.

Steps to reproduce

1. Create a saved database connection in TablePro using SSH tunneling through an AWS EC2 host.
2. Verify that the connection works normally.
3. Leave the connection unused for a few days.
4. Reopen TablePro and try to open the same saved connection again.
5. Observe that TablePro reports a password/authentication error.

Expected behavior

Saved SSH-tunneled connections should reopen normally after being idle for several days, just like local connections.

If credentials are still valid, TablePro should reconnect successfully.

Database type

MySQL / MariaDB

TablePro version

0.30.1

macOS version & chip

No response

Screenshots / Logs

No response