Hello!
I’m trying to setup a fresh Seafile 11 installation with Docker, using the official image/installation guide.
However, whatever I do, something seems fishy with the nginx-server inside the “seafile” Docker container.
A good example is to just Curl the http port:
root@tillberga: /nvme/seafile #> time curl -v http://172.20.0.6:80
* Trying 172.20.0.6:80...
* Connected to 172.20.0.6 (172.20.0.6) port 80
> GET / HTTP/1.1
> Host: 172.20.0.6
> User-Agent: curl/8.5.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Server: nginx
< Date: Fri, 26 Jul 2024 22:36:19 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 0
< Connection: keep-alive
< Location: /accounts/login/?next=/
< Vary: Accept-Language, Cookie
< Content-Language: en
<
* Connection #0 to host 172.20.0.6 left intact
real 0m4.275s
user 0m0.003s
sys 0m0.009s
It takes 4s+ just to respond with the redirect!
This is even confirmed by looking at the access log:
root@tillberga: /nvme/seafile #> tail -n1 logs/var-log/nginx/seahub.access.log
- 172.20.0.1 [27/Jul/2024:00:36:19 +0200] "GET / HTTP/1.1" 302 0 "-" "curl/8.5.0" 4.263
There are no obvious errors in the Docker log or anywhere else, it’s just this slowness that makes the service unusable.
Any ideas about where to start troubleshooting?
EDIT:
It seems like it’s actually the upstream seafile process that is slow to respond.
I get the same result even inside the container running curl http://127.0.0.1:8000.
Still no idea what’s wrong however.