Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOCKS authentication failed. Unexpected number of bytes received. #41

Open
hems opened this issue Jan 29, 2021 · 2 comments
Open

SOCKS authentication failed. Unexpected number of bytes received. #41

hems opened this issue Jan 29, 2021 · 2 comments

Comments

@hems
Copy link

hems commented Jan 29, 2021

For some weird reason i built a new rotating-proxy today and when using the same node.js code to do a request that i used on a previous build I'm getting the following error:

"SOCKS authentication failed. Unexpected number of bytes received."

Running it on an ubuntu image on Digital Ocean.

worth mentioning i had done exactly the same 1 year ago and had been running it as proxy to my node.js app for over an year and that never happened before.

is it possible that something has changed on ubuntu on the image that now requires additional configuration?

@Mr0N
Copy link

Mr0N commented Aug 2, 2021

I have the same problem.

@MRGando
Copy link

MRGando commented Dec 14, 2023

i have the same problem, i'm working on a telegram bot and using node-telegram-bot-api, when i try to connect via proxy i encounter with this error :

SOCKS authentication failed. Unexpected number of bytes received.

here is my code :

const bot = new TelegramBot(token, {
polling: true, request: {
agentClass: Agent,
agentOptions: {
socksHost: '123.45.678.900',
socksPort: '22',
}
}
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants