Junction is a lightweight reverse proxy optimized for efficient TCP and TLS traffic routing. It inspects protocol-level metadata (such as SNI in TLS) to forward encrypted connections to the appropriate backend, without decrypting the traffic. Junction supports both SOCKS5 and SSH proxy protocols (and chaining them), making it ideal for complex egress scenarios where transparent, performant routing is required.
-
π Sni Passthrough
No certificate required, reroutes tls packets using sni header. -
𧦠SOCKS5 Proxy Support
Routes traffic using SOCKS5 proxies, with built-in support for VLESS proxies via Docker image. -
π SSH Proxy Support
Routes traffic using SSH connection as proxy. -
π Proxy Chain Support
Chain multiple proxies together to create complex routing paths and improve privacy or bypass restrictions. -
π³ Dockerized Deployment
Includes a ready-to-use Docker setup for seamless deployment in any environment.
You can grab one of builds from Release page
or use the shell script (please review the scripts before executing it in your shell, or any script you find online who paste them in the shell without checking)
This script requires curl
, tar
, jq
(if version is missing), sha256sum
(optional but recommended) and bash
itself.
Install latest version (requires jq
):
bash <<<"$(curl -fL https://raw.githubusercontent.com/FMotalleb/junction/refs/heads/main/install.sh)"
curl -fL https://raw.githubusercontent.com/FMotalleb/junction/refs/heads/main/install.sh | bash
or select a version manually:
VERSION=0.4.2 bash <<<"$(curl -fL https://raw.githubusercontent.com/FMotalleb/junction/refs/heads/main/install.sh)"
Simply using
go install github.com/FMotalleb/junction@latest
in this method version variables are missing thus you cannot use --version (-v)
to acquire version number
Using:
every build of this application contains singbox internally, but only start singbox if core.singbox
is non-empty value.
The Docker image ghcr.io/fmotalleb/junction:latest-vless
contains a simple bash script entrypoint and basic configuration for sing-box service.
This script is able to parse VLESS_PROXY
to outbound config or receive each field of VLESS proxy as env parameters (see .env.example).
-
Remember: this image requires those env vars to be set.
-
latest-vless
-
{{ .Version }}-vless
contains junction itself based on distroless images by google
latest
latest-distroless
{{ .Version }}-distroless
# Documented example of config file
docker run --rm -it ghcr.io/fmotalleb/junction:latest example
# Save config file to
docker run --rm ghcr.io/fmotalleb/junction:latest example > config.toml
docker run --rm -it \
-v "./config.toml:/config.toml" \
--network host \ # or map each port manually
ghcr.io/fmotalleb/junction:latest -c /config.toml
Remember that the cli has an example
sub command that will be updated more than this section,
Simplest way to run the server is using run
sub command
junction run --help # show help for this sub command
# Simple example of run command that listens on port 8443
# thru socks5 proxy on port 7890 of localhost
# transfers the request to port 443
# of the found hostname using `sni` packets
junction run --listen 8443 \
--proxy socks5://127.0.0.1:7890 \
--target 443 \
--routing sni
-
Include You can include multiple config files (even from a remote http source): Please note that this list is not loosely typed so you have to declare an array of strings
- Support Glob pattern matching
- Support
HTTP
andHTTPS
with basic authentication
include = [ "./*.toml", "http://kamand-pwa.dornicademo.ir/config.toml", ]
-
Core Some specific global configurations are stored here
-
Entrypoints: Top-level array defining routing configurations. Each entry includes:
-
listen
(required): Bind address for incoming connections. Accepts:- Full address:
"IP:port"
(e.g.,"0.0.0.0:8443"
) - Port only:
":port"
(binds to127.0.0.1:port
) - Integer:
port
(binds to127.0.0.1:port
)
- Full address:
-
routing
(required): Target hostname resolution method:sni
: Uses SNI for hostname detection. Default port:443
http-header
: Uses HTTPHost
header. Default port:80
tcp-raw
: Raw TCP forwarding. Requires completeip:port
into
fieldudp-raw
: Raw UDP forwarding. Requires completeip:port
into
field. Note: Proxy not supported
-
proxy
(optional): Upstream proxy configuration. Accepts:- String: Comma-separated proxy chain
- Array: Ordered list of proxy URIs
Supported proxy protocols:
- SOCKS5:
socks5://[user:pass@]hostname:port
- SSH:
ssh://user[:pass]@hostname:port[/path/to/private/key]
- Use either password OR key authentication, not both
Default:
direct
(no proxy)Example proxy chains (equivalent):
"socks5://user:pass@10.0.0.1:1080,socks5://10.0.0.2:1080,ssh://user@10.0.0.3:22/tmp/key"
["socks5://user:pass@10.0.0.1:1080", "socks5://10.0.0.2:1080", "ssh://user@10.0.0.3:22/tmp/key"]
graph LR Client --> Proxy1["socks5://user:pass@10.0.0.1:1080"] Proxy1 --> Proxy2["socks5://10.0.0.2:1080"] Proxy2 --> Proxy3["ssh://user@10.0.0.3:22"] Proxy3 --> Target["example.com:80"]
-
to
(required): Target destination:- For
sni
/http-header
: Port number (string) - For
tcp-raw
/udp-raw
: Complete"ip:port"
address
- For
-
timeout
(optional): Connection timeout duration:- Default:
24h
(orTIMEOUT
environment variable) - Format: Go duration syntax (e.g.,
"50s"
,"5h3m15s"
)
- Default:
-
block_list
(optional) [only when using sni,http-header]: List of hostnames/patterns to block.- Supports wildcards (e.g.,
"*.example.com"
,"glob:*.example.com"
) - Supports Regular Expression (contain check) (e.g.
"regexp:badword"
,"grep:bad.+word"
)
- Supports wildcards (e.g.,
-
allow_list
(optional) [only when using sni,http-header]: List of hostnames/patterns to allow. If specified, only listed hosts are allowed.- Supports wildcards (e.g.,
"*.example.com"
) - Supports Regular Expression (e.g.
"regexp:allowed"
,"grep:.+google.com^"
) - Block rules are applied before allow rules
- Supports wildcards (e.g.,
-
Important Notes:
- Proxy chains execute in order; incorrect ordering breaks the chain
tcp-raw
andudp-raw
require explicitip:port
targetsudp-raw
routing doesn't support proxy protocols- When using
allow_list
, unlisted hosts are implicitly blocked - Wildcard patterns (e.g.,
*.example.com
) match subdomains only, not the base domain
[[entrypoints]]
listen = "0.0.0.0:8443" # Listen IP:Port address
to = "443" # Reroutes connections to this port (defaults to 443)
routing = "sni" # Routing method
proxy = "socks5://127.0.0.1:7890" # socks5 proxy address
[[entrypoints]]
listen = ":8080" # Listen on 127.0.0.1:8080
routing = "http-header"
to = "80" # Defaults from `Host`
proxy = "socks5://127.0.0.1:7890"
[[entrypoints]]
listen = 8090 # Listen on 127.0.0.1:8090
routing = "http-header"
to = "80"
proxy = "direct" # Do not handle using proxy just reverse proxy it directly
[[entrypoints]]
listen = 8099
to = "18.19.20.21:22" # Required for tcp-raw
routing = "tcp-raw" # TCP raw is old behavior where the target address must be specified (used for non-tls non-http requests that do not have any indications for server name nor address)
proxy = "direct" # Do not handle using proxy just reverse proxy it directly
entrypoints:
- routing: "sni" # Routing method
listen: 8443 # Listen ip addr (default ip is 127.0.0.1 if omitted)
to: "443" # Reroutes connections to this port (defaults to 443)
proxy: socks5://127.0.0.1:7890 # socks5 proxy address
- routing: http-header
listen: 8080
to: "80" # Defaults to 80
proxy: socks5://127.0.0.1:7890
You can specify config file path using
--config (-c)
flag (detects config file) Default behavior is to read config fromstdin
usingtoml
format
Use environment variables for dynamic runtime configuration. Below is an example .env
file:
VLESS_PROXY=
HTTP_PORT=80
SNI_PORT=443
These variables help configure VLESS proxies and expose specific endpoints for HTTP/HTTPS traffic.
-
Build the Go application:
go build -o junction
-
Run the application:
./junction --config=config.toml
To build and launch the Docker container:
docker-compose up --build
Once running, the application will be accessible on the configured ports.
A pre-configured .vscode/launch.json
is included for debugging purposes. To debug:
- Open the project in Visual Studio Code.
- Use the "Launch Package" configuration to start debugging.
Junction's project structure is organized as follows:
.
βββ cmd/ # CLI entry point
βββ config/ # Configuration parsing and helpers
βββ docker/ # Docker-related files
βββ router/ # Routers (sni,http,...) logic
βββ server/ # Core server logic
βββ main.go # Main entry point
βββ docker-compose.yml # Docker Compose configuration
This project is licensed under the GNU General Public License v2.0. Refer to the LICENSE
file for more details.