SOCKS5 proxy username+password
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- networking
Research direction
Start at the app’s proxy configuration and connection attempt, then trace how SOCKS5 username and password credentials are handled. The issue does not name files or tests, so locate the relevant entry points first. Done means the app connects to a SOCKS5 proxy with valid credentials, while unauthenticated proxy connections continue to work.
Written by the indexing model from the issue text.
Description
Pre-submission checks
- I am using the latest available release/beta.
- I searched existing issues and this is not a duplicate.
YumaPlayer version
v1.2.0-Beta.4
Affected area
Other
Steps to reproduce
1.Configure a SOCKS5 proxy that requires username and password authentication.
2.Enter the correct proxy host, port, username, and password.
3. Attempt to connect to the proxy.
The connection only works when the SOCKS5 proxy does not require authentication and allows connections without credentials.
When username and password authentication is enabled, the app fails to connect and displays: “Proxy connection failed: SOCKS: authentication failed.”
Expected vs Actual behavior
Expected:
The app should connect to the SOCKS5 proxy when valid username and password credentials are provided.
Actual:
The app fails to connect even when valid username and password credentials are provided.
Android version
Android 16
Device model
Samsung A53
Logs / Crash trace (optional)
No response
Screenshots or screen recordings (optional)
No response
- Dominant language
- Kotlin
- Stars
- 681
- Forks
- 22
- Avg merge
- 16h 5m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MuwMx/YumaPlayer
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MuwMx/YumaPlayer#101 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
MuwMx/YumaPlayer#98 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
MuwMx/YumaPlayer#99 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 44/100
MuwMx/YumaPlayer#96 · 3 comments ·
-
invalid
Difficulty 3/5 1-2 days Newbie friendliness 62/100
MuwMx/YumaPlayer#94 ·
All issues in MuwMx/YumaPlayer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1003 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
droidconKE/droidconKeKotlin#426 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IBRAHIMDANS/i18nSupportPlus#370 · 1 comment ·
Maintainers usually reply within 1 day
-
Crash on Android 14+ when installing extensions: missing FOREGROUND_SERVICE_SHORT_SERVICE permissionOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day