My on-going fun adventure to implement a new standalone Seafile server on Debian
Thought it was going so well until I happened to try editing a markdown file and all I get is a spinning disk. This is a pretty basic install locally on port 8000 so ignore all the shenanigans about Nginx.
Any ideas?

I thought this might be some Debian 13 quirk so I’ve just built a Debian 12.12 install and exactly the same problem. I can edit text files but not markdown files. I followed these instructions to the letter: Installation - Seafile Admin Manual
Some of the pip3 modules throw up depreciation warnings but they appear to install.
It would help if I knew if it was a 3rd party editor that Seafile uses? I’ve heard murmurings of OpenOffice? Grok suggests it’s uses it’s own editor based on Slate.js
Found the problem - this is the default setting for FILE_SERVER_ROOT:
It’s wrong - it should be the DNS name, not IP address. There are hints to this throughout the forums but the thing that caused me to look at this was that not only didn’t editing markdown work, but I couldn’t download any file. This setting must be stored in the database because it’s not defined in any of the configuration files.