FusionAuth 1.37 is released
Have you managed to solve this issue? I am getting the same error log when running the startup script on windows.
@chekikeja I switched back to version 1.36 for now and it is working there as it was prior to this update.
@greggwonderly Using Postgresql worked for me. Although I realized if you had initially selected MySql, this error is still thrown. The solution is to do a fresh installation of fusionauth and only select Postgresql while filling the maintenance mode form.
@chekikeja FYI, windows support is going to come through WSL2 in 1.37 and beyond.
Windows install has been removed. Our strategy is to support Windows using WSL 2 with our provided debian package. Please plan to utilize this strategy, and open a GitHub issue if you encounter issues with the installation.
@greggwonderly Hmm. Interesting.
Were you upgrading?
Do you see this on a fresh install?
What version of mysql are you using?
I have the same problem. Yes, it is a fresh install.
Sorry for the delay here, I've opened a GH issue to identify the cause of this and resolve ASAP.
When using the Docker image you'll need to either use PostgreSQL or build the MySQL JDBC connector into the image.
We've updated the Docker Hub description and the Docker install instructions to make this clearer.
This is a current limitation due our current understanding of the license under which the MySQL JDBC connector is released by Oracle.
You'll need to use WSL v2 or wait for the update which will include a native Windows start script using PowerShell.
Just to close the loop on this, 1.40 includes the native window installation script and there are now instructions on how to install the mysql jar file.