When running web services and files on a home server or NAS, separate access paths, applications, and storage. Back up WordPress files, the database, and storage configuration separately before changes.
Start where the failure appears
- The website returns 5xx: inspect a real 504 investigation separating Cloudflare, Nginx, and PHP responses. Locate the failing layer before disabling WordPress plugins together.
- Syncthing reports The device is not ready or marker missing: begin with drive, mount, and known-file checks plus the preflight code. Do not create a marker in an empty path first.
- Remote administrative access fails: use the home-server remote-access guide to separate Tailscale SSH from public web access. Synology and QNAP are not supported Tailscale SSH servers, so inspect conventional sshd separately.
All WordPress and NAS articles
WordPress rest_no_route: Route, Method or Permission?
Distinguish WordPress REST route, method and permission failures with a CLI example and a read-only script comparing both URL forms.
After Moving a Blog to Oracle: Checking Content, URLs, Images, and a Database Restore
A record of checking content hashes, bilingual URLs, original images, and an isolated database restore after moving a WordPress blog to Oracle, with explicit verification limits.
Recover WordPress When a Plugin Breaks WP-CLI
If a WordPress plugin update causes a fatal error that stops WP-CLI, use --skip-plugins to isolate the plugin and restore the previous version.
Syncthing CLI Ignores –addresses: Verify Version and REST State
Distinguish the historical CLI bug from current configuration, then verify device addresses through the REST API without replacing unrelated device fields.
Syncthing ‘The Device Is Not Ready’: Drive and Mount Checks
Check the real volume, folder path, and files before repairing Syncthing's marker. Covers Windows drives, Linux/NAS mounts, and a custom Marker Name.
Syncthing Tray 2.0.8 Windows Crash: Isolate the Built-in Backend
An evidence-first workflow for separating a Syncthing Tray crash from a backend or device connection failure on Windows.