etunnel for Python
websocket-client based.
Zero registration: every SDK client speaks the same tiny wire protocol
(PROTOCOL.md) against any etunnel server
(default wss://t.ggcode.uk/tunnel).
Install
pip install etunnel
Python >= 3.8 (websocket-client installed automatically).
CLI
etunnel 3000
Prints TUNNEL_URL: https://<subdomain>.t.ggcode.uk — that URL now routes to
your local service. Ctrl-C closes the tunnel.
Embed
from etunnel import connect
t = connect("wss://t.ggcode.uk/tunnel", 3000, {})
print(t["url"])
Environment variables
| Variable | Meaning | Default |
|---|---|---|
ETUNNEL_SERVER |
tunnel server WebSocket URL | wss://t.ggcode.uk/tunnel |
ETUNNEL_LOCAL |
local port or host:port (or 1st CLI arg) |
3000 |
ETUNNEL_TOKEN |
paid-plan API key (optional) | - |
ETUNNEL_SUBDOMAIN |
custom subdomain (paid plans) | random |
License
MIT — see LICENSE. Buffer-based protocol client: request and response bodies are buffered per stream (fine for webhooks/dashboards/demos; use the Go SDK for streaming and WebSocket pass-through).
1 maintainer
Metadata
1 maintainer
Release files for etunnel 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| etunnel-1.1.0.tar.gz | 4.4 kB | With provenance | Details for etunnel-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| etunnel-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for etunnel-1.1.0-py3-none-any.whl |
Total release size: 9.1 kB
Release files / etunnel-1.1.0.tar.gz
| Download URL | etunnel-1.1.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
668f01d47893e81f225bdd1d90c22adfecea94592b1e3a7881a9e66b5816867d
|
|
BLAKE2b-256 checksum How to use checksums |
d5feb64a9394b38fcfe747adf4e85984f25a6a4649ce9f116df26d87fe0ae188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logRelease files / etunnel-1.1.0-py3-none-any.whl
| Download URL | etunnel-1.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60681def687623e12a0c320361b24fe0aeb386b9fe91a168eb5f92f5a78157c1
|
|
BLAKE2b-256 checksum How to use checksums |
06ad2f4e12afb425f3bf0f455a57e06fca9ad1e2dc2e2bac5c9bdfd2e32ff2f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logSecurity for etunnel 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for etunnel-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
