An SSH tunnel lets DbSchema connect to a database server securely through an intermediary SSH host. This is commonly used when the database port is not directly exposed to the internet.
To set up an SSH tunnel, open the SSH Tunnel tab in the Connection Dialog and provide:
~/.ssh/id_rsa).The database host and port in the main Connection Dialog should refer to the database server as seen from the SSH host — often localhost if the database runs on the same machine as the SSH server.
The firewall on the database server may block incoming TCP/IP connections. You need to open the port used by your database:
330654321433152127017If your database was configured to use a non-default port, substitute that value in the commands below.
Open Command Prompt as Administrator and run (replace 3306 with your port):
netsh advfirewall firewall add rule name="DatabasePort" dir=in action=allow protocol=TCP localport=3306
3306)Allow MySQL 3306 InboundOn macOS, the built-in Application Firewall usually controls app-level access rather than raw database ports. For remote databases, the safer and simpler option is often to use an SSH tunnel from DbSchema instead of opening the database port broadly.
If you must expose a local database service, configure the database to listen on the correct interface, then review any host firewall or packet-filter rules that apply in your environment.
Choose the firewall tool used by your distribution.
sudo ufw allow 3306/tcp
sudo ufw reload
sudo firewall-cmd --permanent --add-port=3306/tcp
sudo firewall-cmd --reload
sudo iptables -A INPUT -p tcp --dport 3306 -j ACCEPT
sudo service iptables save
Replace 3306 with the port number for your database.
If DbSchema still cannot connect after you open the firewall, check these in order:
bind-address in MySQL, listen_addresses in PostgreSQL).Use an SSH tunnel when the database should remain private and only a secure jump host is exposed.
The default ports are PostgreSQL 5432, MySQL 3306, and MongoDB 27017, unless your installation uses a custom port.
The most common causes are wrong host/port settings, the database listening only on localhost, missing user privileges, or a separate cloud firewall/security group still blocking traffic.