LODB installation & setup guide.

How the server is laid out

LODB keeps the server application separate from persistent customer data. Users, libraries, metadata, playback state and settings survive normal application upgrades because they are not treated as disposable program files.

Scanning without waiting for the whole library

When LODB discovers a new media item during a scan, it can publish the item into the live catalogue before the entire scan and metadata-enrichment process finishes. Newly discovered media can therefore become visible and playable while the remaining folders continue scanning.

1. Sign in as an administrator and open Libraries.
2. Add a library name, media type and one or more readable filesystem paths.
3. Save the library. LODB starts discovery.
4. Newly found titles can appear in the live catalogue while scanning continues.
5. Metadata and artwork can continue enriching in the background.

Windows Server — full setup guide

1. Download the Windows x64 installer.
   Save LODB_Customer_Server_3.9.33_Tray_Setup.exe to the server PC.
2. Run the installer.
   Approve the Windows UAC prompt. Until the final Authenticode certificate is applied, Windows can show Unknown Publisher.
3. Let setup install the application.
   Program files go to C:\Program Files\LODB Media Server. Persistent customer data is kept separately under C:\ProgramData\LODB Media Server\data.
4. Open LODB from the tray.
   After setup, find the LODB icon near the Windows clock. If Windows hides new tray icons, open the ^ hidden-icons menu. Right-click the icon and choose Open LODB Dashboard.
5. Complete first-run setup.
   On the server PC you can also browse to http://localhost:8098. Create the administrator account and complete the server setup.
6. Add media libraries.
   Add the folders containing the media you are authorised to use. Make sure the Windows account running LODB can read those paths.
7. Connect other PCs.
   From another computer on the same network, use the server PC's LAN address, for example http://192.168.1.50:8098, or use its computer name. The installer adds the LODB program firewall rule for Private/Domain networks.
8. For internet access, use HTTPS.
   Use a domain/reverse proxy and a trusted certificate rather than exposing an unsecured HTTP port directly to the internet.
9. Upgrade safely.
   Run the newer installer over the existing installation. The installer stops the running server/tray process, replaces application files and leaves the persistent data directory intact.

Linux Server — full setup guide

Use the current Linux x86-64 server package on a compatible Linux host. A dedicated service account is recommended so LODB has only the filesystem permissions it needs.

1. Download and extract the Linux package.
   A conventional location is /opt/lodb. Keep the application directory separate from persistent data.
2. Create a service account and persistent directories.

   sudo useradd --system --create-home --home-dir /var/lib/lodb --shell /usr/sbin/nologin lodb
   sudo mkdir -p /opt/lodb /var/lib/lodb/data /var/cache/lodb
   sudo chown -R lodb:lodb /var/lib/lodb /var/cache/lodb

3. Copy/extract the release into /opt/lodb.
   Make the server binary executable, for example sudo chmod +x /opt/lodb/Lodb.
4. Choose the persistent data location.
   The native Linux build follows XDG storage for the service account. You can explicitly keep the main LODB data tree at /var/lib/lodb/data by setting LODB_DATA_DIR=/var/lib/lodb/data.
5. Create a systemd service.

   [Unit]
   Description=LODB Customer Server
   After=network-online.target
   Wants=network-online.target
   
   [Service]
   Type=simple
   User=lodb
   Group=lodb
   WorkingDirectory=/opt/lodb
   Environment=HOME=/var/lib/lodb
   Environment=LODB_DATA_DIR=/var/lib/lodb/data
   ExecStart=/opt/lodb/Lodb
   Restart=on-failure
   RestartSec=5
   
   [Install]
   WantedBy=multi-user.target

   Save this as /etc/systemd/system/lodb.service. If the downloaded archive uses a different executable name/path, use that exact path in ExecStart.

6. Enable and start LODB.

   sudo systemctl daemon-reload
   sudo systemctl enable --now lodb
   sudo systemctl status lodb

7. Give the service account read access to your media.
   Use normal Linux ownership/groups or NAS mount permissions. Avoid solving permissions by making media directories world-writable.
8. Open the dashboard.
   From a browser use http://SERVER-IP:8098, then complete administrator setup and add the media paths as they appear on the Linux host.
9. Upgrade.
   Stop the service, back up persistent LODB data, replace only the application release under /opt/lodb, then start the service again. Do not replace the persistent data directory with the program package.

Docker setup guide

Docker is a deployment method, so there is no general Docker download button. Use a current LODB Docker image appropriate to your host and map persistent server storage outside the container.

LODB Desktop Player — installer & connection guide

1. Run the player Setup EXE.
   Approve UAC and complete installation.
2. Open LODB Desktop Player.
   Use the Start Menu or Desktop shortcut. The connection window waits for you; it does not automatically test localhost.
3. Enter the server address.
   Use a LAN IP such as 192.168.1.50, a computer name such as SERVER-PC, or an HTTPS domain such as media.example.com.
4. Enter the port.
   Local HTTP commonly uses 8098. HTTPS can use 443, 8443 or whichever port you configured.
5. Test Connection.
   The player verifies that the remote endpoint is an LODB Customer Server.
6. Connect to LODB and sign in.
   Your username/password are handled by the Customer Server page. The connection launcher stores the successful server address but not your password.
7. Use Home, libraries, playback and Watch Together.
   The connected interface is server-managed, so library names, permissions, progress and Watch Together remain authoritative on the server.

Backups, updates and recovery

• Back up the persistent LODB application-data directory before major updates, migrations or storage changes.
• Keep media files on their own backup plan; the LODB database is not a backup of the media itself.
• On Windows, application upgrades should replace Program Files while preserving ProgramData customer data.
• On Linux, keep the application release separate from the service account's persistent/XDG state.
• For Docker and UGREEN, keep the same host volume mappings when replacing the image/container.
• After updating, verify sign-in, libraries, artwork, Direct Play, one conversion path, subtitles, audio switching, resume state and Watch Together.