[SOLVED] "Requested page is unavailable" on docker install using mounted NAS as seafile-data drive

[MaxVRAM]

I’ve made some progress, but still am unable to upload files to the seafile server.

Using this forum post from Feb 2020, I gained some insight into using a mounted drive as a data directory:

Moving seafile-data directory to network share, can't create seafile.sock

Hello, I just got Seafile all set up and configured, and it appeared to be working perfectly. However, I’d like to move the seafile-data directory into a network drive location. From the couple of tutorials I’ve found online, the easiest method looked to just symlink the network location into the normal /opt/seafile/seafile-data location. When I attempt to start the service, however, I get the following errors in my seafile.log file: [02/21/20 12:26:06] failed to bind unix socket fd to /op…

Following advice from that post, instead of attempting a symlink on the entire seafile-data directory, I focused on /seafile-data/storage instead. This allowed me to finally log into the web interface.

Here’s a snip of my docker-compose.yml that made this possible:

  seafile:
    image: seafileltd/seafile-mc:latest
    container_name: seafile
    ports:
      - "7006:80"
    volumes:
      - /opt/seafile-data:/shared   # Requested, specifies the path to Seafile data persistent store.
      - /media/nas/seafile:/media/nas/seafile

The notable addition is the bind volume /media/nas/seafile:/media/nas/seafile. From my understanding this allowed me to create a symlink to /media/nas/seafile on my host computer from within the container’s “shared” volume, replacing the /seafile-data/storage directory.

From within the container, I can perform a “touch test” from the syslink’d storage folder, and when navigating to /media/nas/seafile on my host, the “touch” file is there - so I know the syslink is pointing to the right spot on the host.

The issue that still remains is that I cannot upload files either via the web interface nor the Windows client. The Windows client returns a “! Server error” immediately - whereas the web interface allows me to drag and drop folders into a library, but after the upload gets to 100%, returns an “internal error” message.

Any insights would be most helpful.