You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem which I cannot make a head or tails of. I run the app on Chromecast with Google TV (v1, 1080p version, Sabrina) as well as Pixel 7 Pro. I have two different servers - one running in my home network, one in Linode. Both servers are working fine with Outline client (on the phone, it doesn't really work on the TV) - this is how I know that the server itself is functioning.
There's only one remotely exciting thing in the logcat.txt, as per below:
10-22 16:55:29.538 3533 4901 D Vpn : setting state=CONNECTED, reason=agentConnect
10-22 16:55:29.538 3533 4901 I Vpn : Established by com.github.shadowsocks.tv on tun0
10-22 16:55:29.545 7637 9937 E libsslocal: 2023-10-22T15:55:29.540398333+00:00 INFO shadowsocks local 1.15.2 build 2023-02-07T04:07:28.721370700+00:00
10-22 16:55:29.545 3533 3929 D ConnectivityService: NetworkAgentInfo [VPN () - 110] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTING
10-22 16:55:29.547 3509 8093 I netd : networkCreateVpn(110, "true") <0.64ms>
10-22 16:55:29.548 7637 9937 E libsslocal: 2023-10-22T15:55:29.547481999+00:00 WARN no valid UDP server serving for UDP clients, consider disable UDP with "mode": "tcp_only", currently chose 194.233.170.198:1963
10-22 16:55:29.549 7637 9937 E libsslocal: 2023-10-22T15:55:29.549038249+00:00 INFO shadowsocks socks TCP listening on 127.0.0.1:1080
10-22 16:55:29.549 3509 8093 I netd : createNetworkCache(110) <0.03ms>
10-22 16:55:29.549 7637 9937 E libsslocal: 2023-10-22T15:55:29.549388583+00:00 INFO shadowsocks socks5 UDP listening on 127.0.0.1:1080
10-22 16:55:29.550 7637 9937 E libsslocal: 2023-10-22T15:55:29.549794083+00:00 INFO shadowsocks dns TCP listening on 127.0.0.1:5450, local: local_dns_path, remote: dns.google:53
10-22 16:55:29.550 7637 9937 E libsslocal: 2023-10-22T15:55:29.549972624+00:00 INFO shadowsocks dns UDP listening on 127.0.0.1:5450, local: local_dns_path, remote: dns.google:53
10-22 16:55:29.552 3509 8093 I Netd : Destroyed 7 sockets for UidRanges{ 0-99999 } skip={1016 10088} in 1.7 ms
10-22 16:55:29.552 4274 9923 V NativeCrypto: Read error: ssl=0xe8d25428: I/O error during system call, Software caused connection abort
10-22 16:55:29.553 3509 8093 I netd : networkAddUidRanges(110) <1.99ms>
10-22 16:55:29.553 3509 8093 E Netd : getIfIndex: cannot find interface tun0
10-22 16:55:29.554 3509 8093 I netd : firewallAddUidInterfaceRules("tun0", [10000,10001,10002,10003,10004,10005,10006,10007,10008,10010,10012,10013,10014,10015,10016,10017,10019,10020,10021,10022,10023,10024,10026,10027,10028,1068,10029,10030,10031,10032,10033,1073,10034,10035,10036,10037,10038,10040,10042,10044,10045,10048,10050,10051,10054,10055,10057,10060,10061,10062,10063,10064,10065,10066,10067,10068,10069,10070,10071,10072,10073,10074,10075,10077,10078,10081,10085,10086,10087,10089]) -> ServiceSpecificException(22, "[Invalid argument] : Interface rule must specify interface") <0.07ms>
10-22 16:55:29.555 3533 3929 E PermissionMonitor: Exception when updating permissions:
10-22 16:55:29.555 3533 3929 E PermissionMonitor: android.os.ServiceSpecificException: [Invalid argument] : Interface rule must specify interface
(code 22)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.Parcel.createException(Parcel.java:2085)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.Parcel.readException(Parcel.java:2039)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.Parcel.readException(Parcel.java:1987)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.net.INetd$Stub$Proxy.firewallAddUidInterfaceRules(INetd.java:3427)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.connectivity.PermissionMonitor.updateVpnUids(PermissionMonitor.java:573)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.connectivity.PermissionMonitor.onVpnUidRangesAdded(PermissionMonitor.java:488)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.ConnectivityService.updateUids(ConnectivityService.java:5949)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.ConnectivityService.handleRegisterNetworkAgent(ConnectivityService.java:5522)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.ConnectivityService.access$4100(ConnectivityService.java:229)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at com.android.server.ConnectivityService$InternalHandler.handleMessage(ConnectivityService.java:3777)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.Handler.dispatchMessage(Handler.java:107)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.Looper.loop(Looper.java:214)
10-22 16:55:29.555 3533 3929 E PermissionMonitor: at android.os.HandlerThread.run(HandlerThread.java:67)
10-22 16:55:29.555 3533 3929 D ConnectivityService: NetworkAgentInfo [VPN () - 110] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to CONNECTED
10-22 16:55:29.555 3533 3929 W DnsManager: updatePrivateDns(110, PrivateDnsConfig{true:/[]})
10-22 16:55:29.555 3533 3929 D ConnectivityService: Setting DNS servers for network 110 to [/172.19.0.2
I am attaching a snippet of logcat just in case though. The behaviour on P7 Pro appears to be near-identical.
Upon connecting the VPN, all connectivity just dies. Doesn't seem to be DNS issue (I hope, despite some murky messages in the log):
Hey folks,
I have a problem which I cannot make a head or tails of. I run the app on Chromecast with Google TV (v1, 1080p version, Sabrina) as well as Pixel 7 Pro. I have two different servers - one running in my home network, one in Linode. Both servers are working fine with Outline client (on the phone, it doesn't really work on the TV) - this is how I know that the server itself is functioning.
I use the following format for SS configuration:
There's only one remotely exciting thing in the logcat.txt, as per below:
I am attaching a snippet of logcat just in case though. The behaviour on P7 Pro appears to be near-identical.
Upon connecting the VPN, all connectivity just dies. Doesn't seem to be DNS issue (I hope, despite some murky messages in the log):
The text was updated successfully, but these errors were encountered: