[Bug]: Proxy authentication not working with SOCKS4/SOCKS5

[Gabi-Zar]

Guidelines

• I have encountered this bug in the latest release of FreeTube.
• I have encountered this bug in the official downloads of FreeTube.
• I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• I have searched the documentation for information that matches the description of the bug I want to file, without success.
• This issue contains only one bug.
• I have read and agree to follow the rules.

Describe the bug

1. Go to the Proxy settings page
2. Enter a SOCKS5 or SOCKS4 proxy with username and password
3. Click on "test proxy"
4. FreeTube shows the error: Error getting network information. Is your proxy configured properly?
   On my proxy I see a connection attempt without authentication [ERR] socks: Failed to authenticate: No supported authentication mechanism

Expected Behavior

Freetube should connect to the proxy using authentication and the test button should return the proxy IP address

Issue Labels

inconsistent behavior

FreeTube Version

v0.24.0

Operating System Version

Windows 11 version 25H2

Installation Method

.exe

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Upload screenshots or videos

No response

Additional Information

The current proxy authentication implementation use on app.on('login'). However, Electron/Chromium does not emit this event for SOCKS proxies because It does not support it. Using credentials directly in the url (socks5://username:password@ip:port) also does not work. A possible workaround is to run a local HTTP proxy (for example using proxy-chain) that redirect requests to the SOCKS proxy with authentication via an upstream URL.

Nightly Build

• I have encountered this bug in the latest nightly build.

[absidue]

As Chromium doesn't support proxy authentication for SOCKS proxies, we shouldn't be showing the username and password fields when the SOCKS options are selected. So the bug fix will be to only shows those fields for the HTTP and HTTPS options.