Troubleshooting

client.connect() is asynchronous and must be awaited before you use the connection — it only resolves once the TCP handshake (and, if TCPAuth is on, the AUTHENTICATE round-trip) has completed.

// Wrong — races ahead before the connection finishes
client.connect();
console.log(client.authenticatedUser); // undefined
await client.createDB("MyDB");         // "Not connected to server"
 
// Right
await client.connect();
console.log(client.authenticatedUser); // populated
await client.createDB("MyDB");         // works

You're running with TCPAuth: true and sent a command before a successful AUTHENTICATE. Either pass { username, password } in the AxioDBCloud constructor (it auto-authenticates on connect()), or call await client.login(username, password) before any other command.

Your credentials are correct, but the account is still flagged for a forced password change — true for the default admin/admin account and any newly created user. Log into the GUI at http://localhost:27018, sign in, and complete the password change there; there's no TCP command for this yet.

Five failed logins from your IP within a trailing 15-minute window trigger a 15-minute lockout, shared between TCP and the GUI. There's no way to clear the lockout early — double-check credentials or wait it out.

A database literally named config is reserved for AxioDB's own RBAC storage and is blocked on both the GUI and TCP. Use a different database name.

• Confirm the server was started with TCP: true (or, in Docker, AXIODB_TCP=true, the default).
• Confirm the port is published: -p 27019:27019 on docker run, or that nothing else on the host is bound to 27019.
• A protocol error mentioning "Message exceeds maximum size" or "Received HTTP data on TCP port" usually means you're pointed at the GUI port (27018) instead of the TCP port (27019).

See Docker/README.md in the repository for docker logs, port-conflict remapping, and a volume-mounting checklist.