I use seafile v13 (CE, docker-compose). When I try to open a .md file in the editor I get displayed inside the editor:
<div id="header" class="d-flex">
<a href="/" id="logo" aria-label="Private Seafile" title="Private Seafile">
<img src="/media/img/seafile-logo.png" title="Private Seafile" alt="logo" width="" height="32" />
</a>
</div>
<div id="main" class="container-fluid w100 flex-auto ov-auto">
Die Datei ist nicht vorhanden
</div>
But other file types can be opened without problems. Does anybody know why I can’t open md files? My guess is that this is related to the handling of http/https.
My configuration:
On the host system, I have nginx configured as follows:
server {
listen 443 ssl;
server_name myserver.selfhost.eu;
ssl_certificate /mnt/share/seafile-data/seafile/ssl/myserver.selfhost.eu.crt;
ssl_certificate_key /mnt/share/seafile-data/seafile/ssl/myserver.selfhost.eu.key;
location / {
proxy_pass http://127.0.0.1:18080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
location /seafdav {
proxy_pass http://127.0.0.1:8002; # WebDAV HTTP
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
This means that requests are forwarded as http to the seafile container on port 18080.
The docker compose looks like this:
seafile:
image: ${SEAFILE_IMAGE}
container_name: seafile
ports:
- "18080:80"
- "8002:8080" # this is for webdav
...
Some variables in my .env:
SEAFILE_SERVER_LETSENCRYPT=false
SEAFILE_SERVER_HOSTNAME=myserver.selfhost.eu
SEAFILE_SERVER_PROTOCOL=https
When I change SEAFILE_SERVER_PROTOCOL to http, the browser does not load the file due to “mixed content”.
