I rolled back and installed an elastisearch container. Added the SEARCH_TYPE in the fusionauth deployment and mapped a service to the same RDS DB and it stood up without an issue. Something screwy in the way Fusionauth is connecting to either Postgre or MySQL.
I'm going to have to talk to sales as I want to enable the features temporarily to use it as a POC. Also so I can justify the cost per month for actual support beyond forums.
Thank you for your time.
@dan said in Can't get by Maintenance Mode:
That indicates the fusionauth user doesn't have a password provided. https://fusionauth.io/docs/v1/tech/reference/configuration has the configuration values.
If you are using environment variables, you want to make sure
DATABASE_PASSWORDis set.
Using Engine version
14.6
really bizzare.
@dan said in Can't get by Maintenance Mode:
That indicates the fusionauth user doesn't have a password provided. https://fusionauth.io/docs/v1/tech/reference/configuration has the configuration values.
If you are using environment variables, you want to make sure
DATABASE_PASSWORDis set.
Yup have this variable set... stranger still is I can manually connect to the database without issue using the same username and password that I have set in the ENV variables.
did get slightly further. New error:
The user for the username you provided was either created or already existed but could not be granted access to the database. The error from the database was [Access denied for user 'fusionauth'@'10.222.3.159' (using password: NO)].
I'm encountering the same error using PostgreSQL and MySQL.
not at all sure what is happening. I didn't see any mismatch with character encoding.
I also joined your slack channel with a new subchannel https://fusionauth.slack.com/archives/C05R6G25472
with a list of steps and files I used to run this. I can't figure out what FusionAuth is expecting or I'd set it.
-Ian