PrismarineJS / PrismarineJS/node-minecraft-protocol
Socks5 Proxy Authentication Error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
Hello,
I am using the sample program for the socks5 proxy and am receiving the following error:
Client Error FetchError: request to https://authserver.mojang.com/authenticate failed, reason: Hostname/IP does not match certificate's altnames: IP: 13.226.199.74 is not in the cert's list:
at ClientRequest.<anonymous> (/Users//Documents/GitHub/prismarine-viewer/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:390:28)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:28)
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: 'system',
errno: 'ERR_TLS_CERT_ALTNAME_INVALID',
code: 'ERR_TLS_CERT_ALTNAME_INVALID'
}
The socks proxy is working and successfully connects to the server but fails on auth. Ive tried multiple proxies and providers with the same error occurring. Thanks for your help.
@rom1504
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the sample SOCKS5 proxy program and reproduce the request to authserver.mojang.com using the reported proxy setup. Trace the node-fetch request through proxy connection and TLS handling; done means the authentication request no longer fails with ERR_TLS_CERT_ALTNAME_INVALID, or the incompatibility is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100