shadowsocks-android icon indicating copy to clipboard operation
shadowsocks-android copied to clipboard

Published 20 hours ago • verified publisher icon shadowsocks

Fire TV Stick 4K libss-local exits too fast (exit code: 255)

Open kevev opened this issue 4 years ago • 5 comments

Please read contributing guidelines. Thanks.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Install shadowsocks--universal-5.0.5.apk 2.) Attempt to connect.

Expected behavior Connect to Shadowsocks server.

Screenshots If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

  • Android/Chrome OS version: Fire OS 6.2.6.8 (NS6268/2315)
  • Device: Amazon Fire Stick 4K
  • Version: 5.0.5
  • Last version that did not exhibit the issue: 4.7.0 (No error, on connect, but also no internet access when connected.

Configuration Put an x inside the [ ] that applies.

  • [X ] IPv4 server address
  • [ ] IPv6 server address
  • [ X] Client IPv4 availability
  • [ ] Client IPv6 availability
  • Encrypt method: AES-256-CFB
  • Route
    • [ X] All
    • [ ] Bypass LAN
    • [ ] Bypass China
    • [ ] Bypass LAN & China
    • [ ] GFW List
    • [ ] China List
    • [ ] Custom rules
  • [ X] IPv6 route
  • [ ] Apps VPN mode
    • [ ] Bypass mode
  • Remote DNS: dns.google
  • [ ] DNS over UDP
  • Plugin configuration (if applicable):
  • [ X] Auto Connect
  • [ ] TCP Fast Open
  • If you're not using VPN mode, please supply more details here:

Additional context

kevev avatar Feb 28 '20 04:02 kevev

This issue resolved itself afterb3 days. Very weird.

kevev avatar Mar 12 '20 16:03 kevev

still same issue exists+

fr4nk1y avatar Oct 25 '20 12:10 fr4nk1y

Correct, the issue still exists. This issue happened whenever the Fire OS device looses wifi connection and then re-establishes connection. This also happenes after rebooting the Fire OS device. After an hour or so the client is finally able to connect to vpn. Are there any troubleshooting or log gathering steps available?

kevev avatar Sep 21 '21 22:09 kevev

There is another open bug on this. The issue is caused by proxy port 1080 being used by another process. Changing the port number to 1081 for example resolves this issue. The app really should give better error info so the users will know that switching ports is the fix.

kevev avatar Oct 02 '21 02:10 kevev

There is another open bug on this. The issue is caused by proxy port 1080 being used by another process. Changing the port number to 1081 for example resolves this issue. The app really should give better error info so the users will know that switching ports is the fix.

Thanks, Changing port number fixed the issue

javad-vovin avatar Jun 13 '22 05:06 javad-vovin