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

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.

The installer does not format disks or create a new administrator. Hardware cooling starts unconfigured: select the correct wiring and fan type in the panel before relying on PaNasMs to control it.

1. Paste the installation command

During development, choose testing explicitly. There is currently no stable OS release. Testing builds contain recent changes and can have bugs; use backups for data you care about.

curl -fsSL https://panasms.github.io/updates/install.sh | sudo bash -s -- --channel testing

Enter 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 checks that the panel is healthy before reporting success.

Stable releases and inspecting the installer

Once a stable release is available, use the default command:

curl -fsSL https://panasms.github.io/updates/install.sh | sudo bash

Until then, this command stops with an explanation. It never silently selects testing.

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.sh --channel testing

2. 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 -- --channel testing --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 -- --channel testing --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. Finish active transfers and terminal sessions before updating; 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

To inspect what removal would do, run sudo panasms-uninstall --plan. Review that plan before taking further action.

This installer has automated validation and ARM64/AMD64 package builds. Full clean-machine installation acceptance remains in progress; it is not yet a stable-release installation guarantee.