Hello everyone!
I’m having problems with my seafile setup. I’m hosting seafile on my VPS using docker-compose.
My docker-compose:
version: '2.0'
services:
db:
image: mariadb:10.5
restart: always
container_name: seafile-mysql
environment:
- MYSQL_ROOT_PASSWORD=MY-DB-ROOT-PASSWORD
- MYSQL_LOG_CONSOLE=true
volumes:
- seafile-db:/var/lib/mysql
networks:
seafile-network:
ipv4_address: 10.123.1.10
aliases:
- db
memcached:
image: memcached:1.5.6
restart: always
container_name: seafile-memcached
entrypoint: memcached -m 256
networks:
seafile-network:
ipv4_address: 10.123.1.11
aliases:
- memcached
seafile:
image: seafileltd/seafile-mc:latest
restart: always
container_name: seafile
volumes:
- seafile-data:/shared
environment:
- DB_HOST=db
- DB_ROOT_PASSWD=MY-DB-ROOT-PASSWORD
- TIME_ZONE=Europe/Berlin
- SEAFILE_ADMIN_EMAIL=MY-EMAIL
- SEAFILE_ADMIN_PASSWORD=MY-PASSWORD
- SEAFILE_SERVER_LETSENCRYPT=false
- SEAFILE_SERVER_HOSTNAME=MY--SERVER-HOSTNAME
depends_on:
- db
- memcached
networks:
seafile-network:
ipv4_address: 10.123.1.12
aliases:
- seafile
volumes:
seafile-db:
seafile-data:
networks:
seafile-network:
driver: bridge
driver_opts:
com.docker.network.bridge.name: br-seafile
enable_ipv6: false
ipam:
driver: default
config:
- subnet: ${IPV4_NETWORK:-10.123.1}.0/24
My NGINX config:
server {
listen 80;
listen [::]:80;
server_name MY-DOMAIN-NAME;
return 302 https://$server_name$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name MY-DOMAIN-NAME;
include /etc/nginx/conf.d/tls.conf;
client_max_body_size 0;
add_header Content-Security-Policy "default-src 'none'; connect-src 'self'; font-src 'self' data:; img-src 'self' data:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
location / {
proxy_pass http://10.123.1.12:80;
proxy_read_timeout 1200s;
proxy_set_header Host $host;
proxy_set_header Forwarded "for=$remote_addr;proto=$scheme";
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Connection "";
proxy_http_version 1.1;
client_max_body_size 0;
}
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break;
proxy_pass http://10.123.1.12:80;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 0;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
proxy_request_buffering off;
}
location /seafdav {
proxy_pass http://10.123.1.12:80;
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-Host $server_name;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 36000s;
client_max_body_size 0;
}
location /media {
proxy_pass http://10.123.1.12:80;
proxy_read_timeout 120s;
proxy_set_header Host $host;
proxy_set_header Forwarded "for=$remote_addr;proto=$scheme";
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Connection "";
proxy_http_version 1.1;
client_max_body_size 0;
}
}
shoeper
October 20, 2021, 11:10am
2
When you run top on the server while uploading what shows wa/%wa? (Could also be worth to look for disk utilization on the client.)
What is the latency between you and the VPS?
When you transfer data over SSH, does it constantly utilize your connection?
1 Like
What ist wa/%wa?
My output from running top (using docker-compose, so we only see relevant data):
seafile
root 1693450 1693430 0 10:56 ? 00:00:00 /usr/bin/python3 -u /sbin/my_init – /scripts/enterpoint.sh
seafile-memcached
systemd+ 1682604 1682581 0 10:38 ? 00:00:07 memcached -m 256
seafile-mysql
systemd+ 1693219 1693199 0 10:55 ? 00:00:16 mysqld
My latency is on average 21ms.
Transferring with scp is extremely slow, too. Is the seafile transfer similiar to scp? I don’t have this problem using torrent-based transfer (only server and client involved).
That got me debugging further: I also checked using linux on the client-side. I could both transfer via scp and seafile full speed. So it doesn’t seem to be an server issue.
Any idea, what could make a windows-client that slow? I will try to get my hand at another windows-system to check if it’s only this system or all windows systems.
@shoeper : Thank you for pointing me at transfering data over scp. As this was not working as expected I suspected there had to be something wrong with my local machine.
1 Like