For system operators

Run your own WebSDR

PhantomSDR-Plus is built to be run by one radio amateur on one ordinary Linux computer — installed by a single script, kept on the air by its own watchdog, managed from a browser and updated with one command.

Installation

One script does it all

Nothing to prepare by hand — no dependency list, no Node.js to fetch, no OpenCL packages to hunt down. The installer asks every question first — the receiver (the one plugged in is recognised), what to receive, your callsign and locator, your address on the internet and the extras you want — and then installs everything on its own, without asking anything more.

  • Installs every build dependency with your own package manager.
  • Builds the backend, and the driver for the SDR you pick, with its udev rule.
  • Writes the receiver's .toml and site_information.json from your answers, so frequency, sample rate and ports always agree.
  • Builds the desktop and /mobile pages and detects the right OpenCL provider.
  • Adds the admin panel, the FreeDV RADE decoder and the statistics server (each optional).
  • Picks OpenCL only when a device really answers, sets up start at boot if you want it, and starts the receiver.
  • Writes install.txt: every step as OK / SKIPPED / PARTIAL / FAILED.
git clone https://github.com/sv1btl/PhantomSDR-Plus
cd PhantomSDR-Plus
bash install.sh
chmod u+x *sh
Only one port has to be open on your router: 9000. The receiver page, the admin panel, FreeDV RADE, the statistics and the WebSDR relay all go through it. Change any answer later with bash configure-station.sh — it moves the ports and restarts everything for you. The public port must be 1024 or more: for port 80, forward the router's port 80 to 9000. https:// as well is one more question, or later bash setup-https.sh — see Secure Access. With https:// on, the router forwards two more ports to this computer, each to the same port: TCP 443 → 443 and TCP 80 → 80 (Let's Encrypt needs both exactly; port 80 then no longer goes to 9000). Already running your own reverse proxy (nginx, Nginx Proxy Manager, Apache, Traefik)? Choose it at the same question: nothing is installed, your proxy forwards to port 9014, and bash configure-station.sh --proxy-guide prints exactly what it needs — see Your own reverse proxy.
SystemScript
Ubuntu 22.04 / 24.04 / 26.04, Debian 12 / 13bash install.sh
Fedorabash install_fedora.sh
Archbash install_arch.sh
openSUSE Tumbleweedbash install_opensuse.sh

Tested on air on Debian 12 and 13 and Ubuntu 22.04 and 24.04. Ubuntu 26.04, Arch and Tumbleweed are verified to build and start in containers.

Fedora, Arch and openSUSE build clFFT from source when the distribution does not package it. On Fedora and openSUSE the installer also opens the public port in firewalld and labels the panel's logs for SELinux, so everything comes back after a reboot; on a station installed before, run ./setup_admin.sh --firewall and ./setup_admin.sh --selinux once.

Receivers

Bring the SDR you have

IQ or real sampling, from a 2 MHz RTL stick to 70 MS/s direct sampling of the whole HF spectrum. A setup script adds a receiver to a station that is already installed.

ReceiverExampleAdd later with
RX-888 MkII0–30 MHz direct sampling, real signal, s16setup-rx888-udev.sh
RTL-SDR / Blog V42.048 MS/s IQ, e.g. the 2 m bandsetup-rtlsdr.sh
Airspy HF+ Discovery912 kS/s IQ via SoapySDRsetup-airspyhf.sh
SDRplay RSP1A8 MS/s, libmirisdr-5 or SDRplay APIsetup-rsp1a.sh
RigExpert Fobos SDRHF direct sampling, 50 MS/ssetup-fobos.sh
HackRF One10 MS/s, e.g. broadcast FMsetup-hackrf.sh
Start & stop

A launcher with its own watchdog

Each receiver has one self-contained start script. It launches the receiver → spectrumserver chain, detaches it from your terminal, restarts it in place if anything dies, brings up the RADE sidecar and waits to confirm your directory registration — then prints a summary.

  • Live log on screen while starting, -q for two quiet lines.
  • Readable progress in logwebsdr.txt; the server's own output in a rotating spectrumserver.log.
  • Crash diagnostics in crash.log, also readable from the admin panel.
  • Registers on sdr-list.xyz, sdr.shbrg.nl and websdr.org.
./start-rtl.sh       # start, or cleanly restart
./start-rtl.sh -q    # the same, quietly
./stop-websdr.sh     # stop, for any receiver
  ✔ server is up   (spectrumserver + rx888_stream running)
  ✔ RADE sidecar running
  ✔ websdr.org registered (your.host.example:9000)
  · SDR directory posting enabled

Several receivers on one computer

An RX-888 for HF and an RTL-SDR for 2 m, side by side — each a complete server with its own page details, waterfall, chat and markers, living in its own instances/<name>/ folder that an update never overwrites.

Add one

./add-receiver.sh asks which receiver and what it covers, installs the driver, writes the instance and receivers.toml, and offers to start it.

One public port

proxy.py routes each visitor by ?rx=, a cookie or the host name, so all receivers share the public port — and so do RADE, the statistics and the relay.

Start them all

start-all.sh starts every listed receiver; stop-websdr.sh <name> stops just one. Two receivers can even use the same driver program.

Listeners can show the other receivers under their waterfall (Show All) and are taken to the right receiver by frequency. That needs nothing on the server: each strip is a waterfall-only connection, not counted as a listener, at about 10 KB/s of upload for each listener who turns it on.

Admin panel

Manage the station from a browser

A password-protected control panel, so you never need SSH for day-to-day work.

  • Dashboard with server state, CPU, memory, disk and temperature, and a System Health card: every receiver on air or off with its uptime, free disk and log sizes, the last crash entry, and whether RADE V1 and V2 are ready.
  • A Receivers page: every receiver with the range it covers, its bandwidth and whether it is on air; change any receiver's settings and gain (RX888 and RTL), stop and start it, rename or delete it, set the volume a first-time listener starts at and its IQ for listeners (on or off, wide IQ up to 48 kHz and how many may have it at once), or add a new one — all from the panel.
  • Settings with ▶ START / ■ STOP for the start and stop scripts, the listener port shown beside the spectrumserver port, and an HTTPS card that checks https — also through your own reverse proxy — or guides you through turning it on.
  • Config and site-information editors, markers, and a command terminal.
  • Log viewer, chat history and moderation, messages to listeners on the waterfall.
  • Connected users with their names, a kick button and an 8, 16 or 24-hour ban, across every receiver.
  • Alerts by email or Telegram when a receiver goes off the air, restarts or crashes, or the CPU overheats.
  • One-zip backup and restore of the station's settings, and private visitor statistics for up to 31 days.
  • Spot-reporting control, with an hourly schedule for each band and mode and an optional automatic start after a reboot, and graphs of CPU, temperature and users over 24 hours.
  • Six themes, from the classic green terminal to light and an automatic day/night mode, and a layout that works on a phone.

An optional statistics server also shows CPU, RAM and temperature on the receiver page itself.

PhantomSDR-Plus admin panel dashboard
The admin panel dashboard.
Protection

Safe to leave running

🌡️Thermal guard

Thresholds are derived from your own CPU's critical point. The response is staged — warn, lower the clock ceiling, stop the server, and resume once the CPU has been cool for five minutes. It ships in log-only mode, with a test field to prove the whole path before you arm it.

CPU limitwarnthrottlestopresume
Intel 100 °C88929575
Ryzen 95 °C83879070
Raspberry Pi 85 °C73778060

🛡️Connection limits & flood guard

Cap simultaneous listeners and new connections per address, and bound the silent half-open connections no other limit can see. A refused listener is told why. Off by default.

Below it, setup-firewall.sh adds an optional nftables layer that sheds volume before the server reads a byte — and cannot lock you out of your own machine.

🔀Diversity relay

Listeners can pair your receiver with a second site in their browser; only a classic WebSDR as the partner needs a small relay on your server.

🥝KiwiSDR client emulation

An optional bridge on the same host and port lets AetherSDR, kiwiclient and other Kiwi software use your receiver. Enable it with [kiwi_emulation] enabled = true.

Updating

One command, and your site stays yours

update.sh compares your tree with the published one file by file — no git needed — shows what would change, and asks before it writes anything. Every file is one of three kinds:

  • Never touched: your configs, markers, admin password, frequency lists, chat and logs.
  • Asked about only if you edited them: start scripts, service units, the band plan — keep mine, take upstream, or both. Every release carries the fingerprint of every published version, so a file that is merely old is updated without a question.
  • Everything else: updated, after a backup into one dated archive.

It stops the receiver first, rebuilds only what changed — the server, the web page or both — without asking, and starts back exactly what it stopped.

bash update.sh                  # report, then "Update these files now?"
bash update.sh --check          # report only — for cron
bash update.sh --from FILE|DIR  # from a ZIP or a folder, no network
bash update.sh --restore LAST   # undo the last run
Already running PhantomSDR-Plus? Don't install it again — fetch update.sh once from the repository and let it bring everything else.
Performance

Measured on real stations

The cost is the band, not the listeners: once the FFT is done, each extra listener costs almost nothing. With OpenCL the GPU takes the heavy part.

MachineReceiver & rateCPU loadListeners
Ryzen 5 2600RX-888 MkII, 64 MHz sampling, 32 MHz IQ38–40 %50 listeners add under 1 %
Radeon RX 580RX-888 MkII, 64 MHz sampling, 32 MHz IQ28–35 %should handle many
Intel i5-6500T + OpenCLRX-888 MkII, 60 MHz sampling, 30 MHz IQ10–12 %100 is no problem

Ready to build one?

The installation guide covers system preparation, every receiver, the .toml settings, systemd services and troubleshooting.