[Bug][Web][Self Hosting]: connection refused on self hosted VidBee Web when using mounted drive

[lausan3]

Observed behavior and screenshots

Hi all. I'm trying to set up VidBee to work on my Tailscale network.

When running the Docker container locally using the default docker-compose.yml, I am able to use the web app as normal. However, when trying to modify the download directory to my network samba share on a separate NAS using the below modifications, the app paints the UI, tries to load for 4 seconds (during which all buttons are unresponsive), then shows me a "failed to fetch" error. The console error messages tell me that the rpcs have their connections refused, but I'm unsure why.

Anyone have experience with this or have ideas? Much appreciated.

Logs or screenshots

# docker-compose.yml
services:
  api:
    image: ghcr.io/nexmoe/vidbee-api:latest
    environment:
      VIDBEE_API_HOST: 0.0.0.0
      VIDBEE_API_PORT: 3100
      # appended the 
      VIDBEE_DOWNLOAD_DIR: /mnt/cloud/youtube-downloader/data/downloads
      VIDBEE_HISTORY_STORE_PATH: /mnt/cloud/youtube-downloader/data/vidbee/vidbee.db
    ports:
      - "3100:3100"
    volumes:
       # Neither default works either
      - vidbee-downloads:/mnt/cloud/youtube-downloader/data/downloads
      - vidbee-data:/mnt/cloud/youtube-downloader/data
    restart: unless-stopped

  web:
    image: ghcr.io/nexmoe/vidbee-web:latest
    depends_on:
      - api
    ports:
      - "3000:3000"
    restart: unless-stopped

volumes:
  vidbee-downloads:
  vidbee-data:

App version

1.3.14

OS version

Linux Debian