Common Issues with HeidiSQL

❌ Error 1045: Access denied for user

Symptom

Access denied for user 'username'@'host' (using password: YES)

Possible causes

• Incorrect password or unknown user

• User not allowed to connect from current host

• MariaDB server not accepting external connections

Solutions

1. Double-check credentials: username and password must match.

2. Run the following command in MariaDB to list users:

   SELECT user, host FROM mysql.user;

3. Grant privileges if needed:

   GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' IDENTIFIED BY 'password';
   FLUSH PRIVILEGES;

4. In your MariaDB config (my.cnf or my.ini), verify the bind-address setting.

---

❌ Error 10060: Connection timed out

Symptom

Can't connect to MySQL server on 'host' (10060)

Possible causes

• MariaDB server not running

• Port 3306 blocked by firewall

• TCP/IP connections disabled

Solutions

1. Ensure MariaDB service is running.

2. Open port 3306 in your firewall.

3. In the MariaDB config, check for:

   bind-address = 0.0.0.0

4. Restart MariaDB after changes.

---

❌ HeidiSQL crashes or becomes unresponsive

Symptom

App hangs or freezes during certain actions.

Possible causes

• Corrupted configuration files

• DLL conflicts

• Outdated HeidiSQL version

Solutions

1. Close HeidiSQL.

2. Delete config folder at:

   %APPDATA%\HeidiSQL

3. Uninstall HeidiSQL and delete installation directory.

4. Reinstall latest version from https://www.heidisql.com/download.php

---

❌ SSH Tunnel connection fails

Symptom

Cannot connect via SSH tunnel.

Possible causes

• Wrong SSH key

• SSH server unreachable

• Misconfigured tunnel settings

Solutions

1. Test SSH connection outside of HeidiSQL.

2. Recheck SSH key path in HeidiSQL.

3. Make sure the SSH user has permission to access the DB server.

---

❌ Tables or databases not visible

Symptom

Some databases or tables don’t appear.

Possible causes

• User lacks privileges

• View not refreshed

Solutions

1. Check user privileges:

   SHOW GRANTS FOR 'username'@'host';

2. Refresh the schema list in HeidiSQL.

3. Use a user account with appropriate permissions.

---

If the problem persists, consult the official HeidiSQL documentation or open a thread on HeidiSQL