Frequently Asked
Questions & Answers
Clear, technical answers regarding architecture, networking, security boundaries, and storage operations for Mornye Network Storage.
Mornye Network Storage is an open-source, rootless containerized network storage platform and RFC 4918 WebDAV engine for modern Linux systems. Created and maintained by NavyaXdev, it provides high-performance storage that natively mounts across Windows, macOS, Linux, and mobile media players without heavy web UI bloat.
No. Mornye Network Storage is an open-source Linux self-hosted network storage system and RFC 4918 WebDAV server created and maintained by NavyaXdev. It is an independent server-side project and has no relation or connection to the Flutter/Rust desktop music application known as Mornye (mornyeapp).
Mornye binds its host port to 8001 (mapped to container internal port 8000) to ensure protected coexistence. This ensures that existing daemons or API bridges running on host port 8000 are not killed or interrupted during Mornye operations.
Instead of requiring incoming open ports through your router firewall, the cloudflared connector establishes an outbound, multiplexed encrypted connection directly to the Cloudflare Edge network. All traffic routes through this secure outbound pipe, completely bypassing CGNAT and residential firewall restrictions.
Yes! In Windows File Explorer, click This PC → Map Network Drive, enter your WebDAV URL (e.g. https://mornye.yourdomain.com/dav/), and enter your credentials. Windows natively mounts it as a drive letter. For transferring files over 50 MB, check our Windows connection guide for the standard registry tweak.
Mornye uses OWASP-recommended Argon2id parameters (64 MB memory cost, 3 iterations, and 4 parallel threads). Passwords are never stored in plaintext or logged to terminal outputs or reports.
By default, running sudo ./delete.sh executes a Safe Uninstall: it stops and removes Mornye containers and temporary caches, but strictly preserves your files (storage/), SQLite databases (database/), and backup archives. A complete wipe requires explicit confirmation via --purge.
Explore our operational guides or check the source repository for detailed architecture notes and discussions.