Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.w22.dev/llms.txt

Use this file to discover all available pages before exploring further.

Most issues in MySQL UI fall into a small number of categories: the database server is unreachable, the credentials are wrong, or the MySQL user lacks the necessary privileges. The sections below cover the most common problems and how to resolve them.
This error means MySQL UI could not reach the MySQL server at the host and port you provided.Things to check:
  • Confirm MySQL is running on the target host. From a terminal on the same machine, run: 
    mysql -h <host> -P <port> -u <user> -p
  • Verify the host and port in your MySQL UI connection settings. The default MySQL port is 3306.
  • Check that your firewall or security group allows inbound connections on the MySQL port from the machine running MySQL UI.
The username or password is incorrect, or the MySQL user is not permitted to connect from the MySQL UI server’s IP address.Things to check:
  • Double-check the username and password in your connection settings.
  • The MySQL user account may be restricted to specific hosts. To grant access from any host, run the following in MySQL: 
    GRANT ALL ON *.* TO 'user'@'%' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;
  • If you only want to allow a specific IP, replace % with that IP address.
A timeout means the host was reachable on the network but did not respond within the allowed time. MySQL UI uses a 10-second connection timeout.Things to check:
  • Confirm the host is correct and not behind a VPN or firewall that blocks external access.
  • Try connecting from a machine on the same local network as the MySQL server to rule out a network routing issue.
  • If the server is under heavy load, the connection attempt may time out even when credentials are correct — try again in a moment.
MySQL UI only displays databases that the connected user has access to.Things to check:
  • The MySQL user may have privileges on only a subset of databases. Databases the user cannot SELECT from will not appear in the sidebar.
  • To check which privileges the user has, run in MySQL: 
    SHOW GRANTS FOR 'user'@'host';
  • Ask your database administrator to grant the necessary privileges if you need access to additional databases.
If you’ve made changes (for example, through the SQL editor or an external tool) and the sidebar or table view doesn’t reflect them:
  • Click the Refresh (↺) button in the sidebar toolbar to reload the table list.
  • If you ran DDL statements (CREATE TABLE, DROP TABLE, ALTER TABLE) in the SQL editor, use the sidebar refresh to pick up the schema changes.
  • Data changes (INSERT, UPDATE, DELETE) are reflected when you re-open or scroll the table view.
After an import, MySQL UI reports each failed statement with its statement number and error message.Common causes:
  • Table already exists — add DROP TABLE IF EXISTS before each CREATE TABLE in your dump, or use MySQL UI’s export feature which includes these guards automatically.
  • Syntax errors — dumps generated by a significantly different MySQL version may use syntax not supported by your server. Check the MySQL version compatibility of your dump.
  • Missing database or privileges — the target database may not exist, or the user may lack CREATE or INSERT privileges.
Failed statements do not roll back previously executed statements. After fixing the issues, you can re-run the corrected SQL from the import dialog.
MySQL UI stores saved connection details in your browser’s localStorage.
  • Clearing your browser’s site data, cookies, or cache will erase all saved connections.
  • Connections are tied to the specific browser and device — they are not shared across browsers or synced to other devices.
  • To avoid losing your work, export a SQL dump of your database regularly as an external backup.