wireguard-over-wss
github.com · Egress and tunnels · 1 record · JSON
wireguard-over-wss (jnsgruk) Egress and tunnels
paidanonymousno cardD
| Free tier | no service and no account; it is a configuration recipe plus a shell script unit none; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not applicable; the recipe states no volume; ingress: tcp free_allowance: none published |
| Identity | anonymous no account; the server is a droplet the recipe assumes the reader already has |
| Binding | none the constraint is the same host as wstunnel, since this project adds no code of its own; the recipe says 'droplet' |
| Interface | cli wstunnel plus /etc/wireguard/wss.wstunnel |
| Tooling | wstunnel binary, wg-quick, wstunnel.sh |
| Composes with | identical to wstunnel: needs a server host, then rides a websocket-capable forwarder. |
| Reliability | the client script edits /etc/hosts and reloads dnsmasq; a stale entry survives a failed tunnel start |
| Notes | Counted 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 rung | documented nothing to raise: it is a recipe whose only executable part is wstunnel, which is recorded on its own rung |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | github.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-23 | github.com/jnsgruk/wireguard-over-wss | 220 stars, no releases, last push 2024-07-01 |
More fields (10)
{
"wg_path": "none",
"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'",
"ingress": "tcp",
"volume_tib_month": null,
"volume_stated": "not applicable; the recipe states no volume",
"bytes_transit": "yes",
"transit_note": "the same bytes as wstunnel, through a host the reader is assumed to rent",
"hosting_requirement": "a server host with wstunnel and the WireGuard listener, described in the recipe as a droplet",
"last_release": "none; last push 2024-07-01",
"stars": 220
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable