Yeah using SQLite works normally. I can connect to mysql from a container with the client and the same credentials. I also printed the environment vars from n8n in the short window before it crashed and it had the same details.
Perfect so I suspect the host, username or password is wrong. I am not sure why we don’t log the error anymore as it was very helpful when it said what the issue actually was. It could also be that it can’t connect to the database or the user doesn’t have the correct permissions.
Now you have n8n running with sqlite it might be worth trying the MySQL node with the same database credentials to see if that can connect. It may all be for nothing now though as we will be dropping mysql so you would need to migrate to postgres. You could also just keep using sqlite depending on what you are planning to use n8n for.
It is mostly down to time and resources when comparing it to the amount of users actually running n8n with it. By removing support for it we can then spend that time working on new features, improving testing and stability and maybe look at utilising features Postgres offers more closely without having to think of workarounds for other database platforms.