After switching to testflight, SFM inbounds seem broken (still broken after changing back to AppStore version)
Operating system
macOS
System version
macOS 14.1.1 23B81 arm64
Installation type
sing-box for macOS Graphical Client
If you are using a graphical client, please provide the version of the client.
AppStore 1.6.6
Version
No response
Description
Sing-box fails to handle my traffic (any combo of mixed-in, tun-in, cn and proxy all fail).
- Could be tcp only, because using clash web ui I can see udp connections but no tcp ones.
- Nodes are connected fine, the urltest is done, even the geo*.dat and clash-ui are downloaded properly
Might be related to my previous switching versions. Could the extension somehow break? Even though I've tried many times removing the VPN network extension but still got no luck.
Switches: AppStore 1.6.5 (OK) -> TestFllight 1.7.0 (Failed) -> AppStore 1.6.6 (Failed) -> StandAlone verison 1.6.6 (Failed) -> Now all graphical clients Failed.
The same config can be used via CLI and on iOS (1.6.6).
Could be related to #1073
Reproduction
Maybe switching to and from testflight version without uninstalling will do the trick? Not sure.
Even a simple config with just direct outbound can blackout the network. (The proxy here is only used for downloading geo*.dat)
{
"log": {
"level": "debug"
},
"dns": {
"servers": [
{
"tag": "dns-direct",
"address": "udp://223.5.5.5:53"
}
],
"final": "dns-direct",
"strategy": "ipv4_only"
},
"inbounds": [
{
"type": "tun",
"inet4_address": "172.19.0.1/30",
"auto_route": true,
"sniff": false
}
],
"outbounds": [
{
"tag": "out-proxy",
"type": "tuic"
},
{
"tag": "out-dns",
"type": "dns"
},
{
"tag": "out-direct",
"type": "direct"
}
],
"route": {
"geoip": {
"download_detour": "out-proxy"
},
"geosite": {
"download_detour": "out-proxy"
},
"rules": [
{
"outbound": "out-dns",
"protocol": "dns"
},
{
"outbound": "out-direct",
"clash_mode": "direct"
}
],
"final": "out-direct",
"auto_detect_interface": true
},
"experimental": {
"clash_api": {
"external_controller": "127.0.0.1:9090",
"external_ui": "ui"
}
}
}
Logs
Empty conent
I can't reproduce your problem. Perhaps there is a hidden antecedent between these symptoms that has not yet been discovered.
@nekohasekai Alright, thanks for the effort. I'm going to stick with the headless version for now. I close the issue for now, since I don't think we would have more information soon.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days