mrAceT

This quite hinders me form "going live" with my instance, because I hope/expect (some) people will change instance.. this results in an error now because the necessary steps can not...

I initiated a migration form an other server to mine.. and.. everything is crashing.. not only "aliases" crashes.. but practically everything in the profile... **practically no updating of the profile...

I’ve had help of an other mastodon instance owner. It appears that I have bricked the whole S3 thing somehow. I’ll keep this topic open, and tell more when I’ve...

@nightpool thanks for your reply. And indeed, not a bug, maybe a problem with incomplete documentation.. I have figured it out, this is the correct setup if you want AWS-s3...

@doppelgrau @oandradesanchez Thank you! It took me several hours to find this solution, much appreciated I got it working again (Nextcloud Version 25.0.7) , the steps I performed: - deactivating...

This got me thinking, could the cause be that the update process does not take into account that there might be an "old coolwsd process" still active in memory, thus...

I did a server update and got a non working Office again.. I had this "deja vue" feeling.., now I know why: https://github.com/CollaboraOnline/richdocumentscode/issues/186#issuecomment-1579477529 ;) I'll document this now :P

I've tried to find the right spot to put my 2 cents in, hope this is that spot.. IMHO, it would greatly help when some basic theme adjustments would be...

Same issue here, version 4.0.2, using AWS S3 for storage (not at Amazon) And the fix mentioned earlier (https://github.com/mastodon/mastodon/issues/21258#issuecomment-1323137725) worked for me too!

It sounds a bit like the problem I had, have you tried this solution: https://github.com/CollaboraOnline/richdocumentscode/issues/186#issuecomment-1579477529