MultiConnectMultiConnectDocs Website home
MultiConnectCloud › Database Deployments

15. Troubleshooting

Messages on the create form

Message What to do
Name must be between 3 and 60 characters. Shorten or lengthen the Deployment Name
Name may contain letters, numbers, spaces, hyphens and underscores, and must start with a letter or number. Remove other characters
A deployment with this name already exists in the project. Pick another name
This project already has 20 deployments, which is the maximum. Delete a deployment, or use another project
Select a hosting plan. / Select a database engine and version. / Select a region. Make a choice in Basic Info
Use letters, digits and underscores, starting with a letter. Fix the Database Name or Username
MySQL allows at most 64 characters. / MySQL allows at most 32 characters in a username. / PostgreSQL allows at most 63 bytes. Shorten the name
'…' is one of MySQL's own schemas. / '…' is one of PostgreSQL's own databases. Pick another database name
Usernames cannot start with 'mc_' — that prefix is reserved. / 'pg_' is reserved for PostgreSQL's own roles. Pick another username
Use at least 12 characters … Use a longer password, or leave it blank to have one generated
"…" is not a valid IP address or CIDR range. / "…" has a prefix length outside 0 to 32. (or 128) Fix the entry in Allowed Networks
… does not currently have 2 separate hosts with room for the … plan. Every database needs two machines. Try a smaller plan, another region, or later
Select a cache size. Pick a Cache Plan, or turn the cache off
A cache password must be between 12 and 128 characters. / A cache password cannot contain … Change the cache password, or leave it blank
Not available for this plan That region cannot host the chosen plan. Pick another region or plan

Problems after creating

Problem or message What it means What to do
Cannot connect, or the connection times out Almost always the allowed list Add your server's public address (Section 5). If the query console works, this is the cause
Certificate or hostname errors The client is not using the certificate file, or is connecting by another name Download the file (Script 6.1) and connect to the hostname exactly as shown
Read-only error on INSERT, UPDATE or DELETE You sent a write to the reader endpoint Send writes to the writer endpoint
A row you just wrote is missing on the reader Replication is asynchronous Read your own writes from the writer
Too many connections The pool across all your servers exceeds the plan's Max Connections Shrink each pool, or change plan
Start the database before changing its plan … The database is stopped Select Start, then change plan
This database is holding about … GB and the … plan allows … GB. Your data does not fit the smaller plan Free space, or choose a larger plan
The database has to be running to take a backup. / … to restore into it. The database is stopped or busy Start it, or wait for the current change to finish
A backup could not be started right now — … The previous backup is still running, or another change is in progress Try again when it has finished
That backup is from … and this database is … Backups restore only into the same engine and version Use Restore to new deployment
Type the deployment's name exactly to confirm an in-place restore. The typed name did not match Type the name exactly, including case
"…" resolves to a private or reserved address. The import source is not reachable from the internet Make the source reachable, or upload a dump instead
An import is already running on this deployment. One import at a time Wait for it to finish
This database has run 30 console statements in the last minute. Console rate limit Wait a moment
Another operation is already running on this database. A change is in progress Wait for it to finish
The API deployment "…" is linked to this database. Unlink it first … Delete is refused while an API is linked Unlink it from the API's Linked Database section
Running on one copy of the data. in Replica Status The second copy is being rebuilt, usually after a failover Nothing. It clears when the rebuild finishes
Lost the database password It is shown only once Restore a backup into a new deployment with a new password, then move your application to it
The cache is empty It was restarted, resized or replaced Expected. Your code must treat a cache miss as normal