Skip to content

Releases

GHOSTWIRE v0.12.1

Choose a tag to compare

@danielredetzke danielredetzke released this 14 Oct 18:35

Correct addresses in pairing codes and setup links behind a reverse proxy, and a peers list that fits again.

Changes

  • Pairing codes and setup links behind a reverse proxy. The pairing code for the iOS app always said https://, and setup links behind nginx said http:// because nginx doesn't send X-Forwarded-Proto by default. Both now use the address you opened the web interface with: through a reverse proxy that is HTTPS unless the proxy sends X-Forwarded-Proto: http, and on a direct plain-HTTP connection it is http://. Behind a proxy the pairing code no longer carries a certificate fingerprint, as the app sees the proxy's certificate.
  • Peers list no longer scrolls sideways. The Endpoint column shows the address without its port (hover for the full endpoint), and long IPv6 addresses wrap.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.12.1-linux-amd64
sudo ./GHOSTWIRE-v0.12.1-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.12.1-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.12.1-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.12.1-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.12.0

Choose a tag to compare

@danielredetzke danielredetzke released this 13 Oct 16:21

Install behind a reverse proxy in one step, and Settings that make clear what saves at once.

Changes

  • Install behind a reverse proxy. install -proxy 127.0.0.1:8080 sets GHOSTWIRE up for nginx, Caddy or another proxy in front of it: plain HTTP on a loopback address, without asking for a domain or email. A bare port such as -proxy 8080 means 127.0.0.1. The README has examples for nginx and Caddy.
  • Settings save the same way everywhere. Settings that apply at once are switches. Cards with typed values have a Save button that stays off until something changes and shows "Unsaved changes", and leaving the page with unsaved changes asks first. Address and HTTPS says next to its Save button that it takes effect after a restart.
  • Sturdier settings changes. A settings change that fails inside the server now returns an error and is logged, instead of leaving the web interface and API unresponsive until the service is restarted.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.12.0-linux-amd64
sudo ./GHOSTWIRE-v0.12.0-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.12.0-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.12.0-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.12.0-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.11.1

Choose a tag to compare

@danielredetzke danielredetzke released this 11 Oct 20:02

Passkeys now work in browsers that send extra extension data, and a failed passkey sign-in says why.

Changes

  • Passkey sign-in. Some browsers return extension results that were never asked for, such as appid, when signing in with a passkey. GHOSTWIRE refused these sign-ins, so a correctly set-up passkey or YubiKey was rejected, with "this passkey is not known here" when signing in with the passkey alone. Such results are now ignored, for the passkey alone and for a passkey as the second step after the password.
  • Clearer passkey errors. "this passkey is not known here" now appears only for a passkey that belongs to no user on this server, for example one left on a security key from an earlier installation. A known passkey that fails a check gets "the passkey was not accepted", and the log names the reason.
  • Peer search by IPv6. The search on the Peers page also finds peers by their IPv6 address. The list itself still shows the IPv4 address only.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.11.1-linux-amd64
sudo ./GHOSTWIRE-v0.11.1-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.11.1-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.11.1-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.11.1-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.11.0

Choose a tag to compare

@danielredetzke danielredetzke released this 09 Oct 00:28

GHOSTWIRE now has its own DNS setting, and a service restart is one button away.

Changes

  • DNS for GHOSTWIRE's own lookups. A new card under Settings → DNS chooses the servers GHOSTWIRE asks for the update check, the geo databases, Let's Encrypt and public IP detection: the system resolver from /etc/resolv.conf (the default) or servers of your own, Quad9 or up to eight custom IP addresses, asked in order. With your own servers, the system resolver can stay on as a fallback for when none of them answers. Test looks up api.github.com with the settings on screen before you save them. Other programs on the server and the DNS in device configs (set under Server) are not affected.
  • DNS queries in the log. Every lookup is logged with the name, the server that answered, the answer and the time it took; failed lookups say which servers were asked. The Log page has a new DNS filter.
  • Restart service. Settings → Upkeep has a Restart service button. It restarts the web interface and the API; VPN connections stay up. The notice that a setting needs a restart now appears next to that setting instead of at the top of the page.
  • Internal errors. When a request fails inside the server, the client gets a short message and the details (paths, system errors) go to the log only.
  • Fewer writes. Saving settings that did not change, and opening an unknown or expired setup link, no longer rewrite config.json. An unknown setup link no longer generates keys.
  • IPv6 tunnel network. New installations and takeovers of an IPv4-only pivpn use fd00:b00b:5::/64. Existing servers keep their network.
  • README. Checked against the code: install flags with descriptions and defaults, the dev setup, routing options, backups and service flags.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.11.0-linux-amd64
sudo ./GHOSTWIRE-v0.11.0-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.11.0-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.11.0-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.11.0-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.10.3

Choose a tag to compare

@danielredetzke danielredetzke released this 08 Oct 15:52

An install without questions now finds the server's address on its own.

Changes

  • Endpoint with install -y. Without -domain or -endpoint, an install with -y now uses the server's detected public IP as the address devices connect to, the same default the questions offer. Before, the endpoint stayed empty: install printed https://<server address>/ and client configs had no usable endpoint until it was set under Server. If the IP cannot be detected, install says so and points to -endpoint.
  • README. The one-line install is shown first. The unattended install explains that the binary is downloaded first and the admin password is passed in with echo.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.10.3-linux-amd64
sudo ./GHOSTWIRE-v0.10.3-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.10.3-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.10.3-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.10.3-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.10.2

Choose a tag to compare

@danielredetzke danielredetzke released this 08 Oct 15:32

Fixes for taking over pivpn and for peers without DNS.

Changes

  • Password first. install -y reads the admin password from standard input before it changes anything. Without one, or with one that is too short, it stops and the server stays as it was. Before, a pivpn takeover without a password stopped halfway and left a config behind.
  • Never next to pivpn. Install refuses to run while pivpn's WireGuard (wg-quick@wg0) is running or enabled, for example after going back to pivpn, and says how to go on. A takeover that fails before pivpn is stopped removes its config again.
  • pivpn's NAT rules. The takeover removes pivpn's NAT rules (iptables-persistent or ufw) and comments them out for the next boot, so the NAT setting in GHOSTWIRE now decides. Before, peers still reached the internet with NAT switched off. A failed takeover and GHOSTWIRE uninstall put the rules back.
  • No DNS for a peer. A peer set to no DNS ("dns": []) keeps that setting. Before, it was saved as the server default and the config got the server's DNS servers. Empty AllowedIPs are refused.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.10.2-linux-amd64
sudo ./GHOSTWIRE-v0.10.2-linux-amd64 update

Servers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

On a server that took over pivpn with an earlier version, pivpn's NAT rules are still there. To remove them, run sudo /opt/ghostwire/GHOSTWIRE install -y once after the update; it keeps all settings and restarts the service.

Files

File For
GHOSTWIRE-v0.10.2-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.10.2-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.10.2-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.10.1

Choose a tag to compare

@danielredetzke danielredetzke released this 08 Oct 11:16

The update pill in the sidebar now always shows the update state.

Changes

  • Update pill. Next to the version at the bottom of the sidebar, a green “Up to date” pill shows when the last check found no newer release. A newer release shows as an orange “vX.Y.Z available” pill, and the dot on Settings is orange too. With the check switched off, not run yet or failed, the pill is hidden. Both pills open Settings → Updates.
  • API. GET /auth/me has upToDate: true when the last check found nothing newer.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.10.1-linux-amd64
sudo ./GHOSTWIRE-v0.10.1-linux-amd64 update

Servers on v0.10.0 show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.10.1-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.10.1-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.10.1-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.10.0

Choose a tag to compare

@danielredetzke danielredetzke released this 08 Oct 10:57

Updates now come from GitHub only, and every page shows the copyright and the licence.

Changes

  • Updates from GitHub only. The daily check, the release notes and the update commands under Settings → Updates use GitHub. The choice between Gitea and GitHub is gone, together with its setting: an old source value in config.json is dropped the next time the settings are saved. Servers that checked Gitea switch to GitHub with this update. The install script (curl -fsSL https://ghostwi.re/install | sh) also downloads from GitHub.
  • Footer. Every page ends with “© 2026 Daniel Redetzke · MIT License”. The licence links to the LICENSE file on GitHub.
  • Version pill. The version at the bottom of the sidebar is a pill that opens its release notes on GitHub in a new tab. When a newer release exists, the update pill sits next to it.
  • API. updates in GET /settings no longer has source and sourceUrl.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.10.0-linux-amd64
sudo ./GHOSTWIRE-v0.10.0-linux-amd64 update

Servers on v0.9.1 show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.10.0-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.10.0-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.10.0-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.9.1

Choose a tag to compare

@danielredetzke danielredetzke released this 07 Oct 11:55

Devices taken over from an IPv4-only pivpn server no longer send their IPv6 traffic around the tunnel.

Changes

  • pivpn takeover adds ::/0 to a full tunnel. pivpn without IPv6 gives clients AllowedIPs = 0.0.0.0/0 only, so a phone or laptop with IPv6 sends that traffic directly instead of through the VPN. When install takes over such a server, GHOSTWIRE's client default now also includes ::/0, so new configs send IPv6 into the tunnel, where the server drops it. Servers that already have ::/0, and split tunnels, are imported as before. Devices keep their current configs after the takeover; issue a new config to a device to include ::/0 there too.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.9.1-linux-amd64
sudo ./GHOSTWIRE-v0.9.1-linux-amd64 update

Servers on v0.9.0 show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.9.1-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.9.1-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.9.1-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS

GHOSTWIRE v0.9.0

Choose a tag to compare

@danielredetzke danielredetzke released this 06 Oct 13:31

The Dashboard now tells you whether your browser is behind the VPN, and GHOSTWIRE installs with one command.

Changes

  • Protection check on the Dashboard. A new card shows the address websites see for your browser next to the server's address. Through a full tunnel both are the server's and the card says "You are protected", with the peer you are connected as. Directly, or through a peer that only routes the VPN network, it says "Not protected" and shows your own address with its country and network, looked up on the server. The server address is the WireGuard endpoint. GET /api/v1/status has the same information in the new visitor field.
  • One-line install. curl -fsSL https://ghostwi.re/install | sh downloads the latest release for the server's architecture, checks it against SHA256SUMS and starts install. The script comes from Gitea, with GitHub as the fallback for the download; it can also be fetched directly from either. Arguments after sh -s -- go to install.
  • Website. GHOSTWIRE has a home page at ghostwi.re.

Update

Copy the binary for your server to it and run, as root:

chmod +x GHOSTWIRE-v0.9.0-linux-amd64
sudo ./GHOSTWIRE-v0.9.0-linux-amd64 update

Servers on v0.8.0 show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.

Files

File For
GHOSTWIRE-v0.9.0-linux-amd64 64-bit x86 servers
GHOSTWIRE-v0.9.0-linux-arm64 64-bit ARM, e.g. Raspberry Pi OS 64-bit
GHOSTWIRE-v0.9.0-linux-armv7 Raspberry Pi OS 32-bit
SHA256SUMS checksums: shasum -a 256 -c SHA256SUMS