Stuey3D/VibeSDR sbc-portable-11.0.14

VibeServer Portable 11.0.14 — Raspberry Pi + 9 boards (27 Oct; board cards EXPERIMENTAL)

on GitHub

VibeServer 11.0.14 cards, 27 October 2026

All eleven cards have been rebuilt on VibeServer 11.0.14 and replace the 11.0.13 cards, which have been withdrawn. If you are already running a card, use Install updates on the admin page (or sudo apt update && sudo apt upgrade). No re-flash is needed. The new files carry the version in their names (…-11.0.14-20261027.img.xz).

• Public listing: an error message could be taken for the tunnel address. When Cloudflare refused to start a quick tunnel, VibeServer read the address out of the error line and listed the receiver at a link that could not work. It now accepts only a real tunnel address (thank you Kiko).

Also in these cards: the 11.0.13 security update

We've had important communication from Cloudflare advising us to upgrade to the latest Cloudflare Tunnel connector (cloudflared 2026.10.4). It fixes a certificate trust issue: eight eMudhra (emSign) intermediate certificates were found to use weak private keys, and older versions of cloudflared still trusted them. The new version no longer trusts them. Cloudflare says it has seen no active exploitation.

Also in these cards: the 11.0.12 fixes

From the first real-board test (an Orange Pi One, thank you Nick G4IRX):

• SSH could be left running with Armbian's default root password. Armbian's own first-boot script started it. SSH is now off and cannot start until you switch it on in the admin page (Enable SSH: login vibe with your own password; root can never log in over SSH). Each box now makes its own SSH keys.
• The box answers on IPv6 as well as IPv4. On some networks vibeserversetup.local gave only IPv6 addresses and the page did not open.
• http://vibeserversetup.local/ works on Ethernet with no port number until setup is finished (http://vibeserversetup.local:48000/ still works).
• A box with no Wi-Fi can finish setup. There is a "Disable Wi-Fi / no Wi-Fi present" tick if the box gets it wrong.
• Once set up, the box answers only to the name you chose (http://<name>.local:48000/). The setup name goes, and port 80 is released.
• A USB Wi-Fi adapter plugged in after setup is left switched off until you choose: the setup page asks "New Wi-Fi hardware detected — configure it now?".

The Raspberry Pi cards were never affected by the SSH fault (they are built on Raspberry Pi OS).

VibeServer Portable 11.0.14: ready-to-flash cards for eleven single-board computers. Each card boots straight into a VibeServer that you set up from your phone or any browser.

⚠ Experimental. The new board cards are tested on emulated hardware only.

• The two Raspberry Pi cards are VibeServer Portable, the same card as 11.0.1 that already runs on real Raspberry Pis, including our own Pi 3, now with VibeServer 11.0.14 on it.
• The nine other board cards are new. Only the Orange Pi One has been run on a real board so far (by Nick, G4IRX — his test found the faults fixed in this build). Each one was built and then booted under emulation on a PC (systemd-nspawn and QEMU). In that test the setup page answered on port 48000, the host name was vibeserversetup, nothing was listening for SSH and no SSH service was enabled or running, checked again on the second boot after Armbian's own first-run script (the check the first build lacked), the package was 11.0.14-1, and the read-only seal wrote itself on the first boot. The emulator cannot test Wi-Fi, the setup hotspot, Ethernet, DHCP or the .local name, so on real boards those are untested.
• The first person to flash a board card is its tester. Please tell us how it goes, whether it works or not.
• If a card gives you any trouble, don't fight it. Install the board's own operating system instead, then add VibeServer from apt with one line (see The reliable way below). That is a normal, fully supported VibeServer. These cards exist only to make it easy to get VibeServer onto the hardware. They are not the only way, and not the best-tested way.

Which card for which board

• Each non-Pi board needs its own card. Each one boots from code made for that exact board, so a card for one Orange Pi will not start another. The two Raspberry Pi cards each cover several models.
• The minimum confirmed spec that works well is a Raspberry Pi 2 (quad-core ARMv7, 1 GB). Below that, such as a Pi 1, Pi Zero or a 512 MB board, it may work if you keep to the narrow HF modes, but your mileage may vary and I cannot guarantee that it will run. On a Pi 0 or Pi 1 the card picks the right build for the processor by itself at boot.

Flash it

1. Download the card for your board and its .sha256, and check it:
   • Linux: sha256sum -c <file>.img.xz.sha256
   • Mac: shasum -a 256 -c <file>.img.xz.sha256
2. Write it to a microSD card of 8 GB or more with balenaEtcher, which takes the .img.xz as it is, or Raspberry Pi Imager (Choose OS → Use custom). Skip Imager's own OS customisation; the card sets itself up.

Set it up

• Wi-Fi boards: on the first boot the box raises an open VibeServer hotspot. Join it and the setup page opens on your phone. From there, put the box on your own Wi-Fi, or let it run its own secured hotspot with no home network needed.
• Ethernet: plug in a cable and open http://vibeserversetup.local:48000 from any device on the same network. This works on every board, with or without Wi-Fi.
• The VibeServer admin password is the one you type during setup. There are no passwords of ours on the card, and SSH is off. You can switch SSH on from the admin page if you want it.
• To forget the Wi-Fi from a card reader:
  • On a non-Pi board card, put an empty file called vibeserver-reset-wifi on the small VIBESETUP drive that any computer can see. README-VibeServer.txt there explains this.
  • On a Raspberry Pi card, the file goes on the boot drive, as before.
• Updates without re-flashing: once it is set up, Install updates on the admin page brings the whole box up to date. You only need a new card for a brand-new box.

The reliable way: the board's own OS plus apt

If a card doesn't boot, doesn't come up on the network, or you would simply rather do it yourself:

1. Install the board's own OS:
   • Raspberry Pi: Raspberry Pi OS Lite (64-bit, or 32-bit on a Pi 2/1/Zero).
   • Every other board above: Armbian minimal for that board, from dl.armbian.com.
2. Log in and run:

curl -fsSL https://apt.vibesdr.net/install.sh | bash

1. Run vibeserver to set it up. From then on it is an ordinary apt VibeServer that updates from the admin page or with apt upgrade.

What is on the cards

• Raspberry Pi cards: Raspberry Pi OS Lite (Debian 13), with VibeServer 11.0.14 (the same build as apt 11.0.14-1) and the High Detail maps.
• Other boards: Armbian minimal (Debian 13 "Trixie"), with Armbian's own kernel and boot loader for the board, and the same VibeServer 11.0.14, setup and High Detail maps.
  • The system partition is read-only after the first boot, so a power cut cannot corrupt the card.
  • Settings live on their own partition.

Checksums are attached, one .sha256 per card.