Documentation / Setup / PaNasMs installation
Install PaNasMs on your NAS
Start with a supported Linux installation, paste one command, then open the panel in your browser. The installer downloads PaNasMs, installs its dependencies and prints the address to open.
Before you start
- Debian 13 (ARM64 or AMD64), Raspberry Pi OS 13 (ARM64), or Ubuntu 24.04 LTS (AMD64), with systemd, Python 3, curl and internet access.
- An existing Linux user with administrator (sudo) rights and a password. You will use this account to sign in.
- At least 2 GiB of free space on the system filesystem.
- ARM64 is our hardware-tested target. Debian 13 and Ubuntu 24.04 AMD64 were tested in virtual machines; this does not certify every x64 computer.
PaNasMs installs on your existing Linux OS; this command does not write an SD-card image. On a new Raspberry Pi, first write Raspberry Pi OS 64-bit using Raspberry Pi Imager, configure your user and network, and boot it. Open a terminal on the NAS, or connect to it through SSH. Run the command on the NAS, not on your everyday computer.
Armbian images based on Debian 13 are accepted through their Debian base. Installation and core workflows were tested on Armbian 26.8 (Debian 13), Raspberry Pi 5 and Radxa Penta SATA HAT: storage, file permissions, Docker, cooling, native networking, USB network access, fallback Wi-Fi and Google Drive/Dropbox synchronization. Network configuration uses the existing NetworkManager, Netplan or systemd-networkd provider. This does not imply support for every Armbian image or board-specific fan circuit.
The installer does not format disks or create a new administrator. On Raspberry Pi 5, the independent cooling and SMART monitoring package is installed automatically with its dependencies. Disk-bay fan control starts disabled: select the correct wiring and fan type under Settings → Disk subsystem → Advanced settings. The installer does not add a Raspberry Pi OS package repository to Armbian.
Cloud images often have SSH-key access only. Set a password for your existing administrator with sudo passwd "$USER" before signing in to PaNasMs. You do not need to enable SSH password authentication.
1. Paste the installation command
Stable 0.2.31 is available. The default command installs from the signed stable channel. See the release notes for validated platforms and limitations.
curl -fsSL https://panasms.github.io/updates/install.sh | sudo bashEnter your Linux password if requested. Nothing appears while you type a sudo password; this is normal. Leave the terminal open until the installer reports success and prints the panel address.
The installer checks the OS, architecture, available space and port, verifies the signed catalog and package checksum, then uses APT to install PaNasMs and dependencies, including mdadm for RAID, filesystem and SMART tools, Samba and NFS. It waits up to 60 seconds for the panel to become healthy before reporting success.
Stable releases and inspecting the installer
The default channel is stable:
curl -fsSL https://panasms.github.io/updates/install.sh | sudo bashTo opt into development builds, add --channel testing. Testing is never selected silently.
The script runs with administrator privileges. To read it before running it:
curl -fsSLo panasms-install.sh https://panasms.github.io/updates/install.sh
less panasms-install.sh
sudo bash panasms-install.sh2. Open the panel
Open the address printed in the terminal in a browser on the same network. Sign in with your existing Linux administrator username and password. No separate default PaNasMs password is created.
Review storage, cooling and update settings. Optional modules are installed from Modules. To connect external accounts, follow our Google, GitHub or Dropbox setup guide.
Optional: choose a port or HTTPS
The default is HTTP on port 80. If another application uses it, choose a free port:
curl -fsSL https://panasms.github.io/updates/install.sh | sudo bash -s -- --port 8080
For HTTPS with a locally generated certificate (port 443 by default):
curl -fsSL https://panasms.github.io/updates/install.sh | sudo bash -s -- --https
A locally generated certificate is not automatically trusted by browsers. Install it in your client trust stores, or use a certificate issued for your NAS. Do not expose an HTTP panel to the internet. Neither option configures router port forwarding.
On an installed NAS, an administrator can enable HTTPS on the current port:
sudo panasms-tls enable
# Or use your own certificate and matching private key:
sudo panasms-tls enable /path/to/fullchain.pem /path/to/private-key.pem
Then open the same address and port using https://. Certificate renewal is the administrator's responsibility.
Already have PaNasMs?
Use Settings → System updates. The fresh-install command refuses to replace an existing installation. Choose the Stable channel, check for updates and install. Finish active transfers first; open terminal sessions are closed during installation. Update installed modules when the panel requests it.
Early development installations before 0.2.10 need a controlled migration to the new maintenance safeguards. Follow the maintainer update documentation; do not bypass maintenance checks or try to fix this by uninstalling your NAS.
If something does not work
- Unsupported OS: use Debian 13 / Raspberry Pi OS 13, or Ubuntu 24.04 LTS on AMD64. Other Ubuntu releases and Ubuntu ARM64 are not enabled by this installer.
- Port is busy: choose another port using
--port. - Signature, checksum or catalog expiry error: check the NAS clock and internet connection. Do not disable verification.
- APT or startup failed: retain the terminal output. Packages and configuration may remain; fresh installation does not promise an automatic rollback. Repair the reported package problem before retrying.
To inspect what removal would do, run sudo panasms-uninstall --plan. Review that plan before taking further action.
The installation command was verified on clean Debian 13 and Ubuntu 24.04 LTS AMD64 virtual machines in Proxmox for the 0.2.15 release: dependency installation, Linux administrator sign-in, module installation from the catalog and a restart from the panel. ARM64 remains the physical-hardware target. These installation checks do not certify every module or physical x64 device, and do not certify other distributions or boards.