Skip to content

Synology NAS

Purpose

The Synology NAS (swift.fiddlers.cloud / 10.0.1.5) is the central server at Statler. It hosts media, documents, file shares, and several self-hosted services. This page documents what runs on it, how to access it, and what to do if something goes wrong.

Audience

  • Primary: Hope or whoever is maintaining the household infrastructure
  • Secondary: Anyone helping with technical troubleshooting

Prerequisites

  • Access to Bitwarden (search "swift" or "Synology" for credentials)
  • Network access to 10.0.1.5 or swift.fiddlers.cloud

How to log in

  1. Open a web browser and go to http://swift.fiddlers.cloud:5000 (or http://10.0.1.5:5000).
  2. Enter the username and password from Bitwarden (search "swift" or "Synology").
  3. You are now in the Synology DSM (DiskStation Manager) web interface.

Multiple accounts

The NAS has multiple user accounts for different purposes. All credentials are in Bitwarden under the hostname swift.fiddlers.cloud.

What runs on the NAS

The Synology NAS hosts four main subsystems:

1. Media server (movies and TV)

  • What it does: Stores movie and TV files on the NAS filesystem. These are accessed directly via the Infuse app on the Apple TVs.
  • How it works: Infuse connects to the NAS over the local network using a file share. No separate media server software (like Plex) is needed.
  • If it stops working:
  • Verify the NAS is powered on and connected to the network.
  • On the Apple TV, open Infuse and check if the NAS share is still configured (Settings → Shares).
  • If the share is missing, re-add it using the NAS IP (10.0.1.5) and credentials from Bitwarden.

2. Fiddler Docs (this documentation site)

  • What it does: Runs the MkDocs documentation site you are reading right now, inside a Docker container on the NAS.
  • How it works: A Docker container (mkdocs-server) serves the site on port 8443 and listens for webhook updates on port 5443. When code is pushed to Gitea, a webhook triggers git pull + mkdocs build inside the container.
  • If it stops working:
  • The docs still exist in full on GitHub and GitLab as Markdown files. In a pinch, read them directly there.

  • To restart the container, SSH into the NAS and run:

    cd /volume1/docker/mkdocs
docker compose up -d

  • To rebuild from scratch:

    cd /volume1/docker/mkdocs
git pull
docker compose up --build -d

  • For full technical details: See the README.md in the repository.

3. File server (Ricoh MFP and users)

  • What it does: Provides shared network folders used by the Ricoh printer/scanner for scan-to-email and scan-to-folder, and general file shares for household users.
  • How it works: Standard SMB/CIFS file shares hosted on the NAS, accessible from any computer on the network.
  • If it stops working:
  • Verify the NAS is on and connected.
  • On a Mac: Finder → Go → Connect to Server → smb://swift.fiddlers.cloud
  • On Windows: File Explorer → \\swift.fiddlers.cloud
  • Credentials are in Bitwarden.

4. MayanEDMS (document management)

  • What it does: Runs Mayan EDMS, a self-hosted document management system for organizing and searching scanned/uploaded documents.
  • How it works: Runs as a Docker container on the NAS. Accessed via a web browser (check Bitwarden for the URL and port — search "Mayan").
  • If it stops working:
  • Check if the Docker container is running: SSH into the NAS and run docker ps.
  • Restart if needed using docker compose in the MayanEDMS directory.
  • Credentials are in Bitwarden (search "Mayan").

General NAS troubleshooting

  1. NAS is unreachable: Check that it is powered on (lights on the front panel). If off, press the power button. It takes a few minutes to boot.
  2. Services are down but NAS is on: Log into DSM (http://swift.fiddlers.cloud:5000), check Docker → Container list to see which containers are stopped. Restart them.
  3. Storage warnings: DSM will show alerts if disk space is low. Do not delete files without understanding what they are — ask for help.
  4. NAS needs a reboot: In DSM, go to Control Panel → Power → Restart. Services will come back automatically after reboot.

Do not factory reset

Never factory-reset the NAS unless you have confirmed backups of all data. A reset will erase everything.