[SOLVED]: I have Setuped a Managed Mariadb. But I can't connect to it?
- 3
- Self Hosted
- Databases
- Web

I have Setuped a Managed Mariadb. And I changed the APP_DB_xx to the server IP, Username & Pass . But I can't connect to it?

I get Database not ready. Retrying connection (4)...

Im using IP of the VPS to Connect

but i can connect to the DB using normal CLI

"MariaDB [appwrite]> MariaDB [appwrite]> SHOW TABLES; +--------------------------+ | Tables_in_appwrite | +--------------------------+ | _console__metadata | | _console__metadata_perms | +--------------------------+"

But these tables are automatically created

Anybody there?

Where you have set the server IP fields

Have you restarted your docker environment after changing those values with docker compose up -d
?

In the .env file

Yeah I have restarted Multiple times


These are from MariaDB

They are connected and I see these tables created


Okay. So seems everything intact.

Where you run that?


I have setup a VPS in Vultr with MariaDB installed

I SSHed into the server and ran that command

Into which server The Appwrite Or The MarisDB one?

In the MARIADB

Okay. So first you need to be sure that you're able to ping the db instance from the appwrite

Can you verify that?

Yep. I just Did that. I also used Telnet <MariaDB Ip> <Port>. I connected from Appwrite Container to MariaDB successfully
Recommended threads
- Stuck in "deleting"
my parent element have relationship that doesnt exist and its stuck in "deleting", i cant delete it gives me error: Collection with the requested ID could not b...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
- 1.7.0 Self Hosted Upgrade
Hi, I've tried a fresh install on 1.7.0 and I've also done a fresh install on 1.6.2. 1.6.2 is working fine fresh, update to 1.7.0 and migrate fails Fresh inst...
