
I wasn't upgrading, migrating or anything.. i was changing some proxy settings and env varibles but reverted the changes as soon as i saw that usage was restarting infinitely.
Appwrite doctor states its connected to InfluxDB but the log from usage implies otherwise.
Any suggestions how to fix that.. I reinstalled the dockers and so on but still the same outcome

..and influxdb container is up and running and logs are fine too

did you try recreating the container?

jap results in same output

The "usage" container only crashes/restarts when there is a proxy setup in .docker/config.json.. I tried to manually exclude the container with a docker-compose.override.yml but to no prevail

jap?

proxy? exclude what?

yes I did recreate the container ( jap = yes.. sorry)

As soon as I set up a proxy in config.json the "usage" container cant connect to influxdb which causes it to restart every couple seconds. Appwrite doctor says that influxdb is connected though.

Is it even possible to use a global proxy?

im not really sure π§
Recommended threads
- JSON and Object Support in Collection do...
I am working with Next.Js and Appwrite Cloud, I am relatively New to Appwrite but i have noticed there is no direct support of JSON and Object support in attrib...
- Appwrite REST API Docs in LLM-Friendly F...
Is there a version of the Appwrite REST API documentation available in a format suitable for LLM vector embedding? Specifically, Iβm referring to the following ...
- list() is very slow; eventually shows no...
When I use the web browser to view the collections in my database, the documents they contain are normally displayed within a few seconds. For a few days now, h...
