Robert Wildling

I would like to upvote that. Not being able to stop leads to a loss of a lot of tokens eventually.

Any chance to fix this?

Further things I did: - a SQLite `PRAGMA integrity_check` - Check the rights of the db file itself as well as the parent directory (which must be writeable) That didn't...

Thank you for your feedbacks, @br41nslug & @rijkvanzanten! I did what you told me – I am sorry, I was not aware of the CACHE parameter options! Here is what...

I think I found the problem. As soon as I add "PUBLIC_URL: 'https://localhost:8057'" (port matches the port mapping `8057:8055`) the infos are still written to the database, but Directus does...

Ok, I will keep that in mind. However, it does not explain why 9.23.1 works and everything else afterwards not. Also, on my DigitalOcean instances Nginx is handling the proxies....

@br41nslug Thank you for your feedback! Very much appreciated! I will check the link you post and try to dig deeper. I hope I will then also find the reason...

@stx-chris I currently have these settings, and for the moment they seem to work (Ubuntu 22.04, Docker, DigitalOcean) CACHE_ENABLED: 'true' CACHE_PERMISSIONS: 'true' CACHE_SCHEMA: 'true' CACHE_AUTO_PURGE: 'true'

@stx-chris After applying the changes to the docker-compose.yml, how do you restart your project? A simple "docker compose restart" does not clear my cache it seems... So I wonder if...

@stx-chris I deleted all containers and images. Upon "docker compose up -d" my previous test is valid. Doing the whole process again, then setting `CACHE_AUTO_PURGE` to `false` causes the problem...