mux connection closed: read frame header: EOF #2661
Comments
|
And, yeah, version: "3.8"
services:
sing-box:
image: ghcr.io/sagernet/sing-box:v1.11.4
container_name: sing-box
restart: unless-stopped
volumes:
- ./sing-box:/etc/sing-box/
command: -D /var/lib/sing-box -C /etc/sing-box/ run -c /etc/sing-box/reality.json
network_mode: "host" |
|
Don't mean to spam, just trying to troubleshoot things on my own. I've also tried to:
So, I guess the problem is narrowed down to my client config, but I'm running out of guesses. Routing to the servers, like 1.1.1.1 is in place through Any help, if possible, would be much appreciated! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Operating system
Linux
System version
Ubuntu 24.04.2 LTS on client; 22.04.5 LTS on server
Installation type
Original sing-box Command Line
If you are using a graphical client, please provide the version of the client.
N/A
Version
Description
Thank you for the a great software - I'm trying to make it work, but fail. Read all the docs, examples and tried to get support from anyone using it, but with not much luck.
I'm not a sponsor for now, but I would like to become one, just need to make it work - any help would be much appreciated!
I'm starting
sudo sing-box -c 312266054.json runbut nothing works. I can't see anything in DEBUG mode, except for the following error (also highlighted in the logs attached):+0000 2025-03-01 11:49:33 ERROR [733328326 20.88s] inbound/vless[vless-in]: process connection from clientsIPAddress:51396: mux connection closed: read frame header: EOFIt feels like the connection is established, but for some reason failing. I'm in non-censored environment, so I don't believe it's DPI or something of the kind.
Reproduction
sudo sing-box -c 312266054.json runHere is the client side JSON:
{ "log": { "disabled": false, "level": "debug", "timestamp": true }, "dns": { "servers": [ { "tag": "local-1", "address": "77.88.8.8", "detour": "direct" }, { "tag": "remote-1", "address": "8.8.8.8", "detour": "proxy" } ], "rules": [ { "domain_suffix": [".eu"], "server": "local-1" }, { "domain": ["*"], "server": "remote-1" } ], "strategy": "ipv4_only" }, "inbounds": [ { "type": "tun", "tag": "tun-in", "interface_name": "tun0", "address": [ "172.16.0.1/30" ], "auto_route": true, "strict_route": true, "sniff": true, "endpoint_independent_nat": false } ], "outbounds": [ { "tag": "proxy", "type": "vless", "flow": "xtls-rprx-vision", "server": "MY_SING_ADDRESS", "server_port": 443, "uuid": "7063efdf-d487-4a13-a269-1992583a1b19", "tls": { "enabled": true, "server_name": "mydomain.com", "reality": { "enabled": true, "public_key": "QRiUxmZiPWC0BkmqovBEbuDMlSnHqdUw2FLJ1fsbPxQ", "short_id": "3addf2997314a6cb" }, "utls": { "enabled": true, "fingerprint": "chrome" } }, "multiplex": { "enabled": false } }, { "tag": "direct", "type": "direct" } ], "route": { "rules": [ { "domain_suffix": [".us"], "outbound": "direct" } ], "final": "proxy", "find_process": true, "auto_detect_interface": true, "override_android_vpn": true } }Here is a config from server side:
{ "log": { "level": "debug", "timestamp": true }, "inbounds": [ { "type": "vless", "tag": "vless-in", "listen": "::", "listen_port": 443, "sniff": true, "sniff_override_destination": true, "domain_strategy": "ipv4_only", "users": [ { "name": "myaccount", "uuid": "7063efdf-d487-4a13-a269-1992583a1b19", "flow": "xtls-rprx-vision" } ], "tls": { "enabled": true, "server_name": "mydomain.com", "reality": { "enabled": true, "handshake": { "server": "mydomain.com", "server_port": 443 }, "private_key": "yLyK0AQL-hjEu53NgvnIhHL2xDiXdZJMkDmEGjFtEWE", "short_id": [ "3addf2997314a6cb" ] } }, "multiplex": { "enabled": false } } ], "outbounds": [ { "type": "direct", "tag": "direct" }, { "type": "block", "tag": "block" } ] }Logs
Supporter
Integrity requirements
The text was updated successfully, but these errors were encountered: