Connect Vultr MySQL to Infograph
What it brings in: Every table and view the user can read.
What you need
- A Vultr Managed Database for MySQL.
- Its vultradmin password, shown under Connection Details, or a user you created for Infograph.
- 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://vultradminuser: fix for "The username or password was not accepted.":[password]password: fix for "The username or password was not accepted."@[name].vultrdb.comhost: fix for "We couldn't find that host. Check the host name, then try again.":[port]port: fix for "The host refused the connection. Check the port, and that your database accepts connections from Infograph's address."/defaultdbdatabase: fix for "That database does not exist on this server."?ssl-mode=REQUIREDSteps
Allow Infograph's sync servers
In the Vultr console, open Products, then Databases, and choose your database. On its Overview, find Trusted Sources and click Edit. Add the addresses below and click Save.
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. Connect as vultradmin and run this, with your own password and database name, usually defaultdb.
CREATE USER 'infograph'@'%' IDENTIFIED BY '[strong-password]'; GRANT SELECT, SHOW VIEW ON [database].* TO 'infograph'@'%';Copy the MySQL URL
On the Overview, under Connection Details, click Copy MySQL URL. Vultr gives each database a port of its own, so keep the one in the URL. Then put the user you created, and its password, in place of vultradmin's.
mysql://vultradmin:[password]@[name].vultrdb.com:[port]/defaultdb?ssl-mode=REQUIREDPaste it in Infograph and choose your tables
Open Vultr MySQL in Infograph, paste the string and press Connect. SSL Mode is Required, as Vultr requires. 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 address is private, so only your Vultr network can reach it. Use the public host from Connection Details, or connect through an SSH server in that network under Advanced.
We couldn't find that host. Check the host name, then try again.
Click Copy MySQL URL in Connection Details again rather than typing the host. It ends in vultrdb.com.
The host refused the connection. Check the port, and that your database accepts connections from Infograph's address.
Vultr gives each database a port of its own, not 3306. Copy the port from Connection Details.
The server closed the connection. Check that it allows Infograph's address, and whether it requires an encrypted connection.
Check 51.222.152.247 are in Trusted Sources, and that SSL Mode is Required under Advanced: Vultr accepts only encrypted connections.
The host did not answer in time. Check the host and port, and that your firewall allows Infograph's address.
If the database has trusted sources, add 51.222.152.247 under Trusted Sources on its Overview.
The username or password was not accepted.
Check the user and password. Connection Details shows vultradmin's password. Characters such as @, # or / must be percent-encoded in a string, so @ becomes %40.
Those credentials were not accepted.
Check the user and password in the string, and that the user was created as 'infograph'@'%', so it may connect from outside.
That database does not exist on this server.
The database name is the part after the last / in the string. A new database's is defaultdb.
This server does not offer an encrypted connection. Turn on TLS on the server, or set SSL Mode to Preferred.
Vultr always encrypts its MySQL databases, so the host is probably not the database's own. Copy the MySQL URL again from Connection Details.
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.