Error backing up database

[ttasovac]

I'm testing the backup function. I've created a connection via a SSH tunnel. Whichever db I try to back up, I'm getting the same error:

Error backing up database: Command failed with exit code 2: mysqldump: Got error: 1049: Unknown database 'wordpressure' when selecting the database

But the given database is there and I have no problem backing it up with mysqldump over ssh from the command line. What can I do to fix this?

[mikeburgh]

I assume you can open the databases and their tables etc via the explorer ?

What type of tunnel are you using ? a system SSH one, or a manually configured one?

It sounds like it's connecting.. but then not able access the database, I have added some logging so we can see the command it's running.

I just released version 1.17.31, which added some logging to the command being executed, so we can see what's going on.. can you check the output tab in the panel (change the drop down to DBCode) and share the command that appears there when you try and run the backup ?

Details on how to get the output tab are here (you don't need to enable debugging) https://dbcode.io/docs/debug

[ttasovac]

My tunnel was configured automatically using the ssh config file. And the tunnel itself works:

2025-11-09 06:31:51.527 [info] Tunnel: starting OS SSH tunnel for 'vukomatt' to 'localhost:3306' on local port 62084
2025-11-09 06:31:55.533 [info] Tunnel: SSH tunnel established for 'vukomatt' on local port 62084
2025-11-09 06:31:55.534 [info] Tunnel: opened 'vukomatt'
2025-11-09 06:31:55.769 [info] Connection: opened 'wordpressure' on 'Вукомат' (mariadb:10.3.39-MariaDB)
2025-11-09 06:31:55.841 [info] Auth: Access check for 'backup' - Checking subscription (status=trialing, lifetime=undefined, canceled=false, periodEnd=19.11.2025, 17:56:49)
2025-11-09 06:31:55.841 [info] Auth: Access check for 'backup' - Granted (active until 19.11.2025, 17:56:49)
2025-11-09 06:32:14.693 [info] Backup/Restore: Executing command: mysqldump --verbose --host localhost --port 62084 --user root --result-file /Users/ttasovac/Downloads/wordpressure_backup_2025-11-09.sql wordpressure 

At that point I select that what type of dump I want (data, schema or both), select the folder where I want the dump to be saved to, and after that, I get the 1049 error, but not in the log itself, but in the gui:

Many thanks for looking into this!

[mikeburgh]

No worries, so the command at the last line of that log looks right.. has the right port from the tunnel, setting localhost.. Only thing I can think is maybe it's trying trying to use a socket since it saw localhost, so I am going to do a build with --protocol specifically set and see if that sorts it.

In the mean time, can you try again, and once it errors, get that command from the log and try it ? maybe try adding --protocol=tcp into it so we can confirm that fixes it.. you will need to run this while connected to the DB so the tunnel is up.. which is also why you need to get the command from the logs, as the port will change each time.

[ttasovac]

mysqldump --verbose --host localhost --port 65411 --user root --result-file /Users/ttasovac/Downloads/wordpressure_backup_2025-11-10.sql --no-data --protocol=tcp wordpressure gives me error: 1045: Access denied for user 'root'@'localhost' (using password: NO) but that makes sense because the mysql user needs a password.

If I add the password prompt, the command works as expected:

 ~/Downloads  mysqldump --verbose --host localhost --port 65411 --user root --result-file /Users/ttasovac/Downloads/wordpressure_backup_2025-11-10.sql --no-data --password --protocol=tcp  wordpressure
-- Connecting to localhost...
Enter password: 
-- Warning: column statistics not supported by the server.
-- Retrieving table structure for table wp_commentmeta...
-- Skipping dump data for table 'wp_commentmeta', --no-data was used
etc.

I can also confirm that the command which includes the password prompt but no protocol=tcp will result in the mysqldump: Got error: 1049: Unknown database 'wordpressure' when selecting the database.

[mikeburgh]

Thanks for testing that, and sorry I should have mentioned you will need to supply the password (I set it as an ENV variable when running the command to avoid leaking it anywhere).

I just released version 1.17.33 which has the protocol switch option included.. interesting it falls back to socket even though a port is present when it sees localhost.