Database problems

This page covers the Databases page and connection problems. See Databases for the basics.

I cannot create a database

Why it happens: Your plan has a database limit. The page shows how many you use out of how many are allowed. If it says databases cannot be created, your plan has none.

How to fix it:

1. Delete a database you no longer use, then create the new one.
2. Check your limit in Provisioning Limits on your service page in the client area.
3. If you need more, see Upgrade or open a ticket.
4. As a subuser, you need the database create permission.

I cannot see the password

Why it happens: Only users with the view password permission can see it.

How to fix it:

1. Ask the server owner to grant it, or ask them to give you the password.
2. Or use the rotate password button to make a new one (needs the update permission).

Connection refused or timed out from my plugin

Why it happens: Wrong host or port, or the database address is not reachable from where you are connecting.

How to fix it:

1. Copy the endpoint (host and port) exactly from the Databases page.
2. Use those in the plugin’s config, not localhost.
3. Restart the server after editing the config.
4. If the endpoint is right and it still fails, open a ticket.

Access denied for user

Why it happens: The username, password, or Connections From setting does not match.

How to fix it:

1. Copy the username and password again from the Databases page. Do not type them by hand.
2. Check for extra spaces or missing characters at the start and end.
3. Check the Connections From value shown for the database. The default % allows any address. It is chosen when the database is created.
4. If you rotated the password, update every config that uses the old one.

My password stopped working

Why it happens: Rotating the password creates a new one and the old one stops working at once.

How to fix it:

1. Copy the new password from the panel.
2. Update it in every plugin or app config.
3. Restart the server.

Unknown database

Why it happens: The database name in your config does not match the real name. Real names are longer than the name you typed, because the panel adds a prefix.

How to fix it:

1. Copy the database name shown on the Databases page.
2. Paste that full name into your config.

JDBC connection string

Why it happens: Plugins and Java apps often need a JDBC URL. The panel shows one for each database.

How to fix it:

1. Use the JDBC string shown on the Databases page.
2. Put the username and password in their own config fields if the plugin asks for them separately.
3. Do not include your own values by guesswork. Copy what the panel shows.

Wrong host or port

Why it happens: Some plugins expect the host and port in separate boxes.

How to fix it:

1. The endpoint is shown as host:port. Enter the part before the colon as host and the part after as port.

I want to connect from my own PC

Why it happens: The database endpoint may only be reachable from inside the hosting network, and the Connections From setting may restrict who can connect.

How to fix it:

1. Try the endpoint from the panel with a database tool such as HeidiSQL or DBeaver.
2. Connections From is chosen when you create the database. If it is too strict, create a new database with a value that allows your address (be careful with % on anything public).
3. If it will not connect, the endpoint may not be reachable from outside. Open a ticket to ask what is supported.

Character set or garbled text

Why it happens: The plugin and database disagree on text encoding, so accents and emoji break.

How to fix it:

1. Check the plugin’s config for a character set or encoding setting and set it to UTF-8.
2. If it is still wrong, ask the plugin’s developers.

Connection drops after a while

Why it happens: Databases close idle connections after some time, and some plugins do not reconnect.

How to fix it:

1. Check the plugin config for a connection pool or max lifetime setting and lower it.
2. Restart the plugin or the server.
3. If it happens often, open a ticket.

My database disappeared after a reinstall or change

Why it happens: Databases are managed separately from your server files, but a server deletion, or removing a database, deletes the data. Reinstalling or switching software does not normally remove the database itself, but plugin data may be reset.

How to fix it:

1. Check the Databases page to see if it is still listed.
2. If it is gone, check the Activity page for a delete event. See Activity.
3. If the data is missing and you need it, open a ticket right away.

Deleting a database

Why it happens: Deleting removes the database and all its data for good.

How to fix it:

1. Only delete if you are sure. There is no undo.
2. Export or copy what you need first with a database tool.

Still stuck?

Open a ticket or ask on Discord. See Contact support. Include the plugin name and the error line from the Console. Do not paste your database password.