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
Describe the bug
When the primary listed proxy is completely unreachable, it effectively nullifies fallbacks by continuously attempting to reach the proxy, stopping playback of streams.
To Reproduce
Steps to reproduce the behavior:
Add 203.0.113.0(TEST-NET-3, reserved IP, shouldn't be reachable) to the top of your proxy list, above other proxies that are verified to be working
Visit a Twitch channel that isn't/won't be on your whitelist (including automatic sub whitelist) (e.g. /twitchmedia26)
Expected behavior
The unreachable proxy is skipped and temporarily blacklisted after failing to be reached in a reasonable timeframe.
Screenshots
Desktop (please complete the following information):
OS: Fedora Linux 41
Browser: Firefox 137.0b2
Version: TTV LOL PRO v2.4.0
Additional context
The presence of my additional proxies doesn't affect reproducibility. I originally encountered this bug while socks://pl-waw-wg-socks5-101.relays.mullvad.net:1080 was having issues, but confirmed it isn't limited to SOCKS proxies.
Describe the bug
When the primary listed proxy is completely unreachable, it effectively nullifies fallbacks by continuously attempting to reach the proxy, stopping playback of streams.
To Reproduce
Steps to reproduce the behavior:
203.0.113.0
(TEST-NET-3, reserved IP, shouldn't be reachable) to the top of your proxy list, above other proxies that are verified to be workingExpected behavior
The unreachable proxy is skipped and temporarily blacklisted after failing to be reached in a reasonable timeframe.
Screenshots


Desktop (please complete the following information):
Additional context
The presence of my additional proxies doesn't affect reproducibility. I originally encountered this bug while
socks://pl-waw-wg-socks5-101.relays.mullvad.net:1080
was having issues, but confirmed it isn't limited to SOCKS proxies.The text was updated successfully, but these errors were encountered: