midas

Yeah - don't see any evidence of that in the logs + why would it work again after a restart?

Selfhosted

I just don't see how docker can fuck something like this up honestly, the only thing that can be screwy is permissions when dealing with filesystem mounts - but once you've got that working it should be pretty static.

Giving this a shot, importing everything through the CLI now

It's the LSIO image hooked up to seperate (but also docker) postgres db that's also used for other apps. The data and config directories are bind mounts to the local filesystem. It connects to a samba share via the external storage plugin. It is exposed to the internet through a caddy reverse proxy though (the database isn't)

I'm also a develop and my philosophy is that stack traces are for the developers but they should be translated to informative error messages for the user. Otherwise you're doing security through obscurity.

I run a separate instance of postgres since I also use it for a lot of other stuff.

it seems like restarting shouldn’t help unless it’s something else.

I'm honestly also baffled

I'm giving this a try now - it's true it still saves the files on disk somewhere right? AFAIK at least so, this fits my requirements.

I'm using the LSIO docker image and I could not locate the occ file to fire off the reset - but even then - I didn't need to reset my password anyway..

Unless there's a rust application under that hijab I don't care!

Weid, I've got no issue using fastmail for smtp