Hi, a few weeks ago, I upgraded from seafile 10 bare metal to seafile 12 Docker. Since then, I can’t upload via web interface or iOS. The native Windows Seafile client still works!
How I migrated in detail:
I created an empty Seafile 12 Docker environment first. I excluded the original Caddy and used my central Caddy instead.
.env
SEAFILE_SERVER_HOSTNAME=files.home.net
SEAFILE_SERVER_PROTOCOL=https
Caddy
files.{$DOMAIN-MKF} {
import hsts
reverse_proxy seafile:80
}
After the empty fresh Seafile instance worked, I stopped seafile-docker and only kept the db running.
In the DB I dropped the databases.
From my bare metal db I exported the databases:
mariadb-dump --user=root --password --lock-tables --databases seafile_ccnet-db > /root/seafile_ccnet-db.sql
mariadb-dump --user=root --password --lock-tables --databases seafile_seafile-db > /root/seafile_seafile-db.sql
mariadb-dump --user=root --password --lock-tables --databases seafile_seahub-db > /root/seafile_seahub-db.sql
In the dumps I renamed everything from ccnet-db to ccnet_db etc.
I then imported the dumps into the docker DB:
docker exec -i seafile-mysql mysql -u root -pXXX < /root/seafile_seafile-db.sql
docker exec -i seafile-mysql mysql -u root -pXXX < /root/seafile_seahub-db.sql
docker exec -i seafile-mysql mysql -u root -pXXX < /root/seafile_ccnet-db.sql
Finally, I replaced the empty seafile-docker data dirs, with my original bare metal data dirs:
cp -arf /opt/seafile/seafile-data /opt/stacks/seafile/data/seafile/
cp -arf /opt/seafile/seahub-data /opt/stacks/seafile/data/seafile/
I then started the Docker stack and seafile was upgrade from 10 to 12 and the GUI and native client were up and running.
Only after a few days I noticed, that I wasn’t able to upload anymore. But only through the web interface and the iOS client.
The native Windows client works without issues.
Can somebody please help me?
