In Sing-Box, an inbound
refers to a connection that is incoming to the sing-box. In other words, it is a connection that is initiated by a remote device or client and directed towards the device that is running Sing-Box.
In the Sing-Box configuration file, the inbound
section is used to specify the settings for handling incoming connections. This includes the listening port, protocol, transport, and other settings such as authentication methods.
The inbound handles incoming traffic and directs it to the appropriate local service while the outbound is responsible for connecting to a remote server and forwarding traffic to it.
This is a comprehensive list of inbound connection types that are supported by Sing-Box. You can access the official documentation for each type by clicking on the provided links.
Type | Format | Injectable |
---|---|---|
direct | Direct | X |
mixed | Mixed | TCP |
socks | SOCKS | TCP |
http | HTTP | TCP |
shadowsocks | Shadowsocks | TCP |
vmess | VMess | TCP |
trojan | Trojan | TCP |
naive | Naive | X |
hysteria | Hysteria | X |
tun | Tun | X |
redirect | Redirect | X |
tproxy | TProxy | X |
I have created some working & tested config.json files for a variety of combinations of protocols and transports for sing-box supported inbounds. These can be found under the singbox inbounds tag. you can use these ready json blocks to quickly build your own config.json with your own requirements.
It is important to carefully consider the security and maintenance of any proxy protocol when choosing one for your needs. While some people may believe that VLESS is secure, it is actually unmaintained since 2020. Therefore, many new software tools and platforms, including sing-box, do not support VLESS as inbound.
However, Sing-Box supports VLESS as outbound only for compatibility reasons.
Your favorite feature may be missing because it doesn’t fit, because it compromises performance or design clarity, or because it’s a bad idea.
https://sing-box.sagernet.org/faq/