check that the names of the db in settings and the DB in the actual DB server match. i think the .env or setup has the DB named ninja. but the database was populated with the name db-ninja-01
there was something not working i tried creating a DB with a different name that supplied and it did not work. this is the database name that did work for me.
CREATE SCHEMA db-ninja-01 DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
CREATE USER ‘ninja’@‘localhost’ IDENTIFIED BY ‘ninjapassword’;
GRANT ALL PRIVILEGES ON db-ninja-01.* TO ‘ninja’@‘localhost’;
It sounds like the DB has not been initialized at all. On shared hosting, this could be because the mysql-client lib is not available.
I would suggest running /update?secret= URL
This will attempt to perform the migration independently. If after running this command the DB tables are not created, then most likely the shared hosting platform is not compatible with the application.