Possibly unhandled rejection: about mailcow-dockerized HOT 11 CLOSED

Yeah data is stored in permanent volumes on your filesystem. As long as you don't delete the directory, you shouldn't lose anything

from mailcow-dockerized.

Thanks worked for me and the problem was solved

from mailcow-dockerized.

Try to clean your cache and restart memcached. But this is really not a mailcow issue. :-/

from mailcow-dockerized.

Conveniently I've also just experienced this issue and have cleared my browser cache as well as restart memcached but unfortunately it doesn't fix this issue. It might be worth looking further into this problem

from mailcow-dockerized.

It seems that bringing the cluster down and then up was the necessary solution rather than simply restarting. Don't know why but it works

from mailcow-dockerized.

Hm, that is strange.

from mailcow-dockerized.

i probably made a mistake. I'm still trying to learn docker, in fact when i restored my old config everything worked fine again. It makes sense that this just was a caching issue, not client side (i tried incognito mode and emptied cache). But i'm not 100% sure, still a newbie to dockerized apps

from mailcow-dockerized.

@afzalarsalan how did you bringing the cluster up and down? With start and stop? I have the same issue and want to try your solution.

from mailcow-dockerized.

Yup exactly, just straight docker-compose down && docker-compose up -d. Although I must mention I've been experiencing other weird anomalies with this version of Sogo such as email duplication when reopening folders but not on refresh. Very weird

from mailcow-dockerized.

That means that also all data will be deleted? That is not the right way for me 😄

from mailcow-dockerized.

from mailcow-dockerized.