I've just upgraded Appwrite 1.2.1 to 1.3.8 on the way to upgrading to Appwrite 1.4.4. I've completed the incremental upgrade from 1.2.1 to 1.3.0 and run the migration. I then upgraded through each of the 1.3.x minor releases although in retrospect, I could probably just have jumped straight to 1.3.8.
I have now restarted all the containers only to receive a "Gateway error" when visiting http://localhost/. On further investigation I can see the appwrite-usage container restarting every few seconds with the following error in the logs:
2023-10-10 11:00:36 InfluxDB not ready. Retrying connection (2)...
2023-10-10 11:00:37 InfluxDB not ready. Retrying connection (3)...
2023-10-10 11:00:38 InfluxDB not ready. Retrying connection (4)...
2023-10-10 11:00:39 InfluxDB not ready. Retrying connection (5)...
2023-10-10 11:00:40 InfluxDB not ready. Retrying connection (6)...
2023-10-10 11:00:41 InfluxDB not ready. Retrying connection (7)...
2023-10-10 11:00:42 InfluxDB not ready. Retrying connection (8)...
2023-10-10 11:00:43 InfluxDB not ready. Retrying connection (9)...
2023-10-10 11:00:44 InfluxDB not ready. Retrying connection (10)...
2023-10-10 11:00:44 InfluxDB database not ready yet```
The curious thing is that the influx container appears to be up and running normally - as are all the other Appwrite containers. Any thoughts?
Update: After stopping the appwrite-usage container, I now get an Appwrite login screen, but signing in with an email/password results in a "Server Error" message.
Same result when visiting https://localhost/login
Hmmmm.... Based on several other threads where containers were restarting, I reran the migration script. This appears to have resolved the issue!
Recommended threads
- redirect_uri errors on flutter client
Hi all, I'm using the flutter client for my app to do appwrite auth and use the JWTs to send to my backend. When I try to sign in with SSO, I get this: https:/...
- Cloud 500 error
- float
Hello everyone, So, I created a column of type **float** with the **min** and **required** options, I noticed that it wouldn't let me set a **2 decimal points ...