Our host requires SSH for database connections and it will not connect via Database Manager. I am on a MAC and can connect via SSH from the command line, and can connect via SSH using Navicat. I have the exact same information in database manager and I just get a can’t connect error.
Error is “Error connection: Failed to connect to localhost:45434 in 15000ms” with localhost and
Note: I have tried both Localhost and IP in the database host. I also tested using the wrong password but I get the same can’t connect to localhost error so I’m assuming the SSH is not connected, and as stated above it is confirmed to work via other programs;
I am at a complete standstill until I get this resolved. Has anyone else had this issue, PLEASE help point me in the right direction.
The key was generated on a MAC and is 4k (ssh-keygen -b 4096)
I just noticed this error, I am using the generated key, does anyone have experience with this? :
Error: Cannot parse privateKey: Unsupported key format at Client.connect (/Applications/Wappler.app/Contents/Resources/app.nw/node_modules/ssh2/lib/client.js:225:13) at Server. (/Applications/Wappler.app/Contents/Resources/app.nw/node_modules/tunnel-ssh/index.js:65:23) at Server.emit (events.js:314:20) at TCP.onconnection (net.js:1559:8)
Configuration:
Wappler Version : 3.7.8
Operating System : macOS Big Sur 11.2.1
Server Model: ASP.NET
Database Type: MSSQL
Hosting Type: PLESK
Expected Behaviour:
Connect to the database using SSH Tunnel
As a test, I created a brand new site and get the same error. Any help please!
Actual Behaviour:
Error: Cannot parse privateKey: Unsupported key format at Client.connect (/Applications/Wappler.app/Contents/Resources/app.nw/node_modules/ssh2/lib/client.js:225:13) at Server.<anonymous> (/Applications/Wappler.app/Contents/Resources/app.nw/node_modules/tunnel-ssh/index.js:65:23) at Server.emit (events.js:314:20) at TCP.onconnection (net.js:1559:8)
I see we have some troubles with more advanced encryption algorithms. Specially for keys generated using the ed25519 algorithm. Will see if we can improve our support for those.
You might want to try something like mentioned here, in the mean time.
