Can't use socks5 proxy

• The FAQ doesn't contain a resolution to my issue

Versions

• mineflayer: 4.20.1
• server: vanilla/spigot/paper 1.20.4, also tried others like 1.18 or the default one
• node: v20.17.0

Detailed description of a problem

When using a socks5 proxy, I can connect to the server but I cant log in, spawn, and anything.

What did you try yet?

I tried using other socks5 proxies, but that can't be the problem because I tried using the proxy inside Minecraft with the Meteor Client. It works perfectly. I also tried following the example, following other examples in internet, removing the "agent" argument and keeping the "connect" argument and vice versa, connecting to other servers, etc. I also tried using the fakehost and the host arguments.

Your current code

const bot = mineflayer.createBot({
  username: 'someone',
  version: '1.20.4',
  connect: bot => {
    socks.createConnection({
      proxy: {
        host: proxyHost,
        port: parseInt(proxyPort),
        type: 5
      },
      command: 'connect',
      destination: {
        host: mcHost,
        port: parseInt(mcPort)
      }
    }, (err, info) => {
      if (err) {
        console.log(err);
        return;
      }

      bot.setSocket(info.socket);
      bot.emit('connect');
    });
  },
});

Expected behavior

Being able to log in the server.

Additional context

I'm using linux, specifically Ubuntu 22.04.4, may that affect something?

[fredericodeveloper]

Same thing here.

[officialdakari]

same

[rom1504]

https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/examples/client_socks_proxy/client_socks_proxy.js

[officialdakari]

i already follow that example. only mineflayer has that issue, Minecraft perfectly connects via proxy

[rom1504]

Minecraft or node minecraft protocol?

If you want help provide as much information as possible

[officialdakari]

Minecraft perfectly connects via proxy. It's mineflayer's issue

[rom1504]

Are you interested in solving the problem you are encountering?

[officialdakari]

Yeah, but I don't have any clue. Probably I will use V2ray with iptables as a workaround

[rom1504]

Can you try this https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/examples/client_socks_proxy/client_socks_proxy.js

Then report errors

[aftercares0]

Can you try this https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/examples/client_socks_proxy/client_socks_proxy.js

Then report errors

this connected when disconnects about 2 - 3 seconds after connect:

PS C:\path> node test.js minecaft.xyz 27048 localhost 1080
connected
Connection lost

there's no logs on my mc server too and proxy works fine when im on meteor client w/ proxy
(localhost = 3proxy running on my pc)

[aftercares0]

on some servers it refuses to connect entirely

[rom1504]

Can you enable debug mode and report logs

…

On Sun, Aug 17, 2025, 12:35 r ***@***.***> wrote: *Rylazius* left a comment (PrismarineJS/mineflayer#3457) <#3457 (comment)> on some servers it refuses to connect entirely — Reply to this email directly, view it on GitHub <#3457 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR437V5S5WL3JHOWVMX2ND3OBLHVAVCNFSM6AAAAACD7LJTT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJUGI4TMMRVHA> . You are receiving this because you commented.Message ID: ***@***.***>

[officialdakari]

Nevermind, it actually didn't connect because of SRV record I changed 6b6t.org to play.6b6t.org and it worked 17 августа 2025 г. 11:09:13 UTC, Romain Beaumont ***@***.***> пишет:

…

rom1504 left a comment (PrismarineJS/mineflayer#3457) Can you enable debug mode and report logs On Sun, Aug 17, 2025, 12:35 r ***@***.***> wrote: > *Rylazius* left a comment (PrismarineJS/mineflayer#3457) > <#3457 (comment)> > > on some servers it refuses to connect entirely > > — > Reply to this email directly, view it on GitHub > <#3457 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAR437V5S5WL3JHOWVMX2ND3OBLHVAVCNFSM6AAAAACD7LJTT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJUGI4TMMRVHA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Reply to this email directly or view it on GitHub: #3457 (comment) You are receiving this because you commented. Message ID: ***@***.***>