fshy

Home / Egress and tunnels

wireguard-over-wss (jnsgruk)

github.com/jnsgruk/wireguard-over-wssTool (wireguard transport)egress/wireguard-over-wssJSONcomparereport an errorprovider JSON

Free allowance
No service and no account; it is a configuration recipe plus a shell script
Verdict
self-hosted, last resortverdict paid-only: no free allowance; listed for its price. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost
no price statedsee Price below
Identity
anonymousno card, no phone
Binding limit
noneno named constraint binds
Evidence
documented2 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
Free tierno service and no account; it is a configuration recipe plus a shell script
unit none; metered on none
PriceUSD 0
Bindingnone the constraint is the same host as wstunnel, since this project adds no code of its own; the recipe says 'droplet'
Identityanonymous no account; the server is a droplet the recipe assumes the reader already has
Egressnot applicable; the recipe states no volume; ingress: tcp
free allowance: none published
Interfacecli wstunnel plus /etc/wireguard/wss.wstunnel
Toolingwstunnel binary, wg-quick, wstunnel.sh
Composes withidentical to wstunnel: needs a server host, then rides a websocket-capable forwarder.
Reliabilitythe client script edits /etc/hosts and reloads dnsmasq; a stale entry survives a failed tunnel start
NotesCounted separately because brief names it, but it is not a second implementation: it installs wstunnel, writes a unit file, and wraps wg-quick with a script that rewrites the peer endpoint. Its only unique contribution is the wstunnel.sh wrapper that rewrites /etc/hosts and the interface config, which the wstunnel README does by hand.
Evidence notedocumented nothing to raise: it is a recipe whose only executable part is wstunnel, which is recorded on its own rung
Parsed numbers
  • has-free-tier 0
  • price USD 0
Evidence 2
datesourcewhat it proved
2026-10-23github.com/jnsgruk/wireguard-over-wss"No modifications need to be made to the Wireguard server configuration itself, but wstunnel needs to be installed", and the systemd unit with --restrict-to 127.0.0.1:51820
2026-10-23github.com/jnsgruk/wireguard-over-wss220 stars, no releases, last push 2024-07-01
More fields 9
wg pathnone
wg detail"Wireguard VPN connection to be tunnelled over a secure websockets connection"; the recipe runs wstunnel, not new software: 'wstunnel server wss://0.0.0.0:443 --restrict-to 127.0.0.1:51820'
ingresstcp
volume statednot applicable; the recipe states no volume
bytes transityes
transit notethe same bytes as wstunnel, through a host the reader is assumed to rent
hosting requirementa server host with wstunnel and the WireGuard listener, described in the recipe as a droplet
last releasenone; last push 2024-07-01
stars220
Unknown values 2
  • per object cap stated: the field does not apply to this kind of offer
  • retention stated: the field does not apply to this kind of offer