Connect Azure Database for MySQL to Infograph
What it brings in: Every table and view the user can read.
What you need
- An Azure Database for MySQL flexible server with Public access (allowed IP addresses), or an SSH server that can reach it.
- Permission to edit the server's Networking page in the Azure portal.
- Infograph's sync servers connect from 51.222.152.247.
Your connection string
Each part is one thing you fill in, and each can fail on its own.
mysql://[admin-user]user: fix for "The username or password was not accepted.":[password]password: fix for "The username or password was not accepted."@[server-name].mysql.database.azure.comhost: fix for "We couldn't find that host. Check the host name, then try again.":3306port: fix for "The host refused the connection. Check the port, and that your database accepts connections from Infograph's address."/[database]database: fix for "That database does not exist on this server."Steps
Copy the server name
Open your server's Overview page and copy the Server name. Use the name rather than its IP address, which Azure can change.
Add a firewall rule for Infograph
Open Networking and add a firewall rule for each address below, with it as both the start and the end IP address, then save. A new rule can take a few minutes to apply.
51.222.152.247Create a read-only user
Infograph only reads. Give it its own user so you can see and revoke its access in one place. Run this as the admin user, with your own password and database name.
CREATE USER 'infograph'@'%' IDENTIFIED BY '[strong-password]'; GRANT SELECT, SHOW VIEW ON [database].* TO 'infograph'@'%';Write your connection string
Use the plain user name, without an @server suffix, and port 3306.
mysql://[admin-user]:[password]@[server-name].mysql.database.azure.com:3306/[database]Paste it in Infograph and choose your tables
Open Azure Database for MySQL in Infograph, paste the string and press Connect. Pick the tables you want and Infograph starts loading them.
Allow 51.222.152.247 through your firewall so Infograph can connect.
Connect
Troubleshooting
Each entry is the message Infograph shows when a connection fails. Open it for the fix.
This host is not reachable from Infograph. Use your database's public address.
The name resolves to a private address, so the server uses private access. Connect through an SSH server in that network under Advanced.
We couldn't find that host. Check the host name, then try again.
Copy the Server name again from the Overview page. It ends in .mysql.database.azure.com.
The host refused the connection. Check the port, and that your database accepts connections from Infograph's address.
Check the port, usually 3306, and that SSL Mode is Required. Azure requires TLS 1.2 by default.
The server closed the connection. Check that it allows Infograph's address, and whether it requires an encrypted connection.
The server answered, then hung up before Infograph could sign in. Check it allows 51.222.152.247: some hosts close the connection rather than refuse it. If the server accepts only encrypted connections, set SSL Mode to Required under Advanced.
The host did not answer in time. Check the host and port, and that your firewall allows Infograph's address.
Add a firewall rule for 51.222.152.247 on the server's Networking page, and wait a few minutes for it to apply. A server with private access (VNet integration) has no public address; connect through an SSH server in that network under Advanced.
The username or password was not accepted.
Check the admin user and password. Use the plain user name: the user@server form belonged to the retired Single Server. Characters such as @, # or / must be percent-encoded in a string, so @ becomes %40.
Those credentials were not accepted.
Check the user name has no @server suffix, and the password is right. You can reset the admin password on the Overview page.
That database does not exist on this server.
The database name is the part after the last / in the string. The server's Databases page lists them.
This server does not offer an encrypted connection. Turn on TLS on the server, or set SSL Mode to Preferred.
SSL Mode is set to Required, but the server would not encrypt the connection. Turn on TLS on the server, and check the host is the database's own address rather than a proxy in front of it. Or set SSL Mode to Preferred under Advanced.
Through an SSH server
Infograph could not reach your SSH server. Check its address and port, and that it allows connections from Infograph's address.
Check the SSH server's public address and port, and that its firewall allows 51.222.152.247 on that port, usually 22.
Your SSH server only offers old encryption settings. Infograph needs a current OpenSSH with an Ed25519, ECDSA or RSA (SHA-2) host key.
Your SSH server only offers old encryption settings. Update OpenSSH on it. It needs an Ed25519, ECDSA or RSA (SHA-2) host key.
Your SSH server refused Infograph's key. Check the key is in authorized_keys for that user.
Add Infograph's public key, shown in the form when you turn on SSH, to ~/.ssh/authorized_keys for the SSH user you entered. Check that user exists and that the file is readable only by them.
Your SSH server's identity changed. If you expected this, trust the new server on the connection.
Infograph remembers your SSH server's key from the first connect, and the server now shows a different one. If you rebuilt or replaced the server, open the connection and press Trust the new server. If you did not, ask whoever runs the server before you trust it.
This connection has not trusted an SSH server yet. Open the connection and use Re-discover streams to trust it.
The connection has not checked your SSH server yet. Open the connection and press Re-discover streams. Infograph then remembers the server's key.
Your SSH server would not forward to the database host. Check the permitopen rule and the database host and port.
The SSH server would not pass the connection on to the database. In authorized_keys, the permitopen rule must name the database host and port exactly as you entered them. In sshd_config, AllowTcpForwarding must not be no. The database must also accept connections from the SSH server, for example in its firewall or security group.