Fixes for Common Issues and Errors
View All Tags
Connect Timeout=0 looks as if it should mean "no limit", as it does for many timeouts. In MySql.Data, every pooled connection failed at once with Timeout expired, on a server with nothing else connected.
CREATE command denied to user 'inventory_app'@'172.23.0.1' for table '__EFMigrationsHistory' appeared even though that table already existed. It's what you get when dotnet ef database update runs as an app account that can only read and change rows: exactly how that account should be set up, and exactly why migrations need a different one.
Option not supported (Parameter 'def;sslmode') looked like a typo in an option name, but def was the end of my password. A ; ends a value in a connection string, so the driver read the rest of the password as a new option, and put it in the exception message. That message can end up in your logs.
User 'inventory_app' has exceeded the 'max_user_connections' resource (current value: 5) means the account has reached a limit on connections, and the pool tried to open one more. One account limit and one pool setting need to agree, and until they do, some requests fail.
Connections using insecure transport are prohibited while --require_secure_transport=ON is the server refusing a connection with no TLS, on purpose. MySql.Data puts Authentication to host … failed in front of it, but your password is fine. Your connection string needs TLS turned on.
An account with REQUIRE X509 must present a client certificate. I gave MySql.Data the right one, in SslCert and SslKey, and got Access denied, though the mysql client got in with the same files. The driver reads those PEM files and never sends them.
The host 127.0.0.1 does not support SSL connections means the server didn't offer TLS at all. Mine had offered it a minute before. I'd reloaded its certificates with a wrong key and NO ROLLBACK ON ERROR, which does exactly what it says: when the reload fails, TLS stays off.
TLS protocols TLSv1 and TLSv1.1 are no longer supported is a clear message, and it comes before any connection is attempted: TlsVersion in your connection string names a version the driver has dropped. Change it to what's accepted.
Asking for TLS 1.3 on a Mac gave me The requested security protocol is not supported, though MySQL and .NET 10 both support it. By default, .NET on macOS uses a TLS library that doesn't, and there's a switch to use the one that does.
Cannot determine the frame size or a corrupted frame was received sounds like a damaged network. Nothing was damaged. The driver asked for TLS 1.2, and the server only accepts TLS 1.3, and this is how that disagreement reads from the client's side.
