I'm having huge issues upgrading to 1.6.x - is this supposed to be working or is 1.6 still broken for self hosting?
I have the following issue when coming from 1.5.10 but unable to resolve using the provided docker config.
https://github.com/coollabsio/coolify/issues/4224
appwrite service cannot connect to the db in the logs, and crashes out.
From appwrite service logs:
Database not ready. Retrying connection (1)...
Database not ready. Retrying connection (2)...
Database not ready. Retrying connection (3)...
Database not ready. Retrying connection (4)...
Database not ready. Retrying connection (5)...
Database not ready. Retrying connection (6)...
Database not ready. Retrying connection (7)...
Database not ready. Retrying connection (8)...
Database not ready. Retrying connection (9)...
Database not ready. Retrying connection (10)...
Fatal error: Uncaught Exception: Failed to connect to database: Failed to create connection: php_network_getaddresses: getaddrinfo for redis failed: Name does not resolve in /usr/src/code/app/http.php:84
Stack trace:
#0 [internal function]: {closure}()
#1 {main}
thrown in /usr/src/code/app/http.php on line 84
[2025-02-17 00:56:19 #1.8] ERROR php_swoole_server_rshutdown() (ERRNO 503): Fatal error: Uncaught Exception: Failed to connect to database: Failed to create connection: php_network_getaddresses: getaddrinfo for redis failed: Name does not resolve in /usr/src/code/app/http.php:84
Stack trace:
#0 [internal function]: {closure}()
#1 {main}
thrown in /usr/src/code/app/http.php on line 84
TL;DR
Developers are having trouble getting Appwrite 1.6.x to work with self-hosted Docker. Some are experiencing issues with the appwrite service not connecting to the database, leading to crashes. A developer on Coolify confirmed running 1.6.0 without issues. The provided Docker config is not resolving the problem. The error lies in the appwrite service logs with a failure to connect to the database due to a redis issue. No clear solution was provided in the thread.
