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
{{ message }}
Repository navigation
Commit e08baba
Browse filesBrowse the repository at this point in the historyBrowse files
fix(v2): panel no longer hangs, and the login entry repairs itself
Reported on a fresh install: "everything installs, but the bypass does not turn
on and the program hangs".
The bypass was actually fine - the service was running and YouTube and Discord
answered. Two real problems were behind the symptom.
1) The log flooded and froze the window. A desktop Telegram client that cannot
complete the handshake just reconnects, so the proxy logged a warning per
attempt: measured 72 failed handshakes per 30 seconds, hundreds of lines a
second. The logs page queued one dispatcher operation per line. That is what
looked like a hang.
- Failed handshakes are now counted and reported once every 30 seconds with
the total, plus a hint that the Telegram settings probably carry the web
proxy secret where the local MTProto secret belongs.
- The logs page batches incoming entries and flushes them in one pass.
Measured after the fix: 8 log lines in 40 seconds.
2) The autostart entry pointed at a file that does not exist:
"C:\Program Files\YoutubeDiscordPanel.exe" while the panel actually lives in
"C:\Program Files\YoutubeDiscordPanel\YoutubeDiscordPanel.exe". Nothing in
the UI showed this; the bypass simply never came back after a reboot.
- The panel now rewrites the login entry at every start if it does not match
the running executable. Verified: the broken entry was corrected and logged.
- The installer now always creates a folder named YoutubeDiscordPanel inside
the chosen location instead of dropping files into the picked folder
itself, which is how a mismatched path was written in the first place.
Also: auto-apply after login defaults to ON. A fresh install used to come up in
"panel only" mode, so the remembered strategy was never applied and it looked
like the bypass had not started.
0 commit comments