u/Diligent_Buster

Setup Seafile 13 pro and trying to get seadoc and webdav working.

I followed the installation docs on the seafile website following the seafile 13 setup instructions and installed by downloading the referenced .yml files and editing the .env file.

These are the changes I made after doing a diff of the original with my configured file for .env. Edited to privatize the config.

< SEAFILE_SERVER_HOSTNAME=test.mydomain.xyz < JWT_PRIVATE_KEY=long string of characters

< SEAFILE_MYSQL_DB_PASSWORD='blah'

< INIT_SEAFILE_MYSQL_ROOT_PASSWORD='mypassword'

< INIT_SEAFILE_ADMIN_EMAIL=admin@foobar.com < INIT_SEAFILE_ADMIN_PASSWORD='mypassword'

I can connect to sf, have setup the seadrive clieant and can upload and edit documents.

I'm trying to get document collaboration working but can't seem to access the seadoc or webdav.

When I try to access seafile.mydomain.xyz/seadoc-data I get nothing but a "sorry the requested page cannot be found".

Since seadoc is included in seafile pro 13 (i have 1 user only for testing) how do I get seadoc working so I can setup collaboration? Specifically need to edit spreadsheets and documents. I was hoping to use whatever builtin editors/programs are in seadoc.

The documentations talks about nginx but that is not included in the list of files to setup. The downloaded yml files and .env configure caddy, not nginx

The manual says: $ tree /opt/seafile-data -L 2 /opt/seafile-data ├── logs │ └── var-log ├── nginx │ └── conf └── seafile ├── ccnet ├── conf ├── logs ├── pro-data ├── seafile-data └── seahub-data

but mine looks like:

[root@localhost seafile]# tree /opt/seafile-data -L 2 /opt/seafile-data └── seafile ├── conf ├── logs ├── pro-data ├── seafile-data └── seahub-data

Sorry, I'm not used to docker, caddy, or ngigx.

I'm assuming that i missed something in the .env file. Thanks.

reddit.com
u/Diligent_Buster — 5 days ago

Two servers with windows 2025 and LSI raid both fail to boot.

I think patch tuesday got me. I jut had 2 servers with LSI 9361's and cachecade enabled not come back up. I was out in the field when it happened. The drives virtual drives are "Optimal access blocked". Both servers seem to be missing the cachecade volume. Pretty unlikely that 2 enterprise SSD's completely failed at the same time in both servers. Although I have seen some references to MS killing SSD's. Anyone else experience this? I did not get any alerts that my drives were failing or failed and then on reboot I'm down. Servers are running Server 2025. 256GB ram, 9 1.8 or 1.2 SAS drives in raid 6.

Anyone else recovered from this? I'm reading that you can disassociate the cachecade from the VD's or delete the cachecade and then the system will boot? Anyone else done this? Am I the guinea pig?

I need to get these up. Anyone have experience with this?

reddit.com
u/Diligent_Buster — 1 month ago