read ECONNRESET error

[norket]

while joining the proxy server, mc loading screen stops working and only shows "loading world", ive checked my error logs and this is the code showed afer this happening:

Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' }

ive tried this on 2 diferent machines, a server running ubuntu and my own machine running Arch and in both got similar results (even running diferent nodejs versions)

adding to that, if you try and press Escape kiey while loading screen is frozen, the proxy will start restarting, and then crash.

take in mind that my configuration is the one recomended in the wiki for prio accounts as my test account has priority queue

[Enchoseon]

Could you paste the output of npm run debug-info?

Also, consider switching to the latest stable release (v1.0.4). You'll have to install it with npm install, but if you can get it to run without getting error #1, v1.0.4 is a lot more stable than the main branch at the moment.

[norket]

im using 1.0.4, also the npm run debug-info doesnt output anything. i forgot to mention that the versions of node that im using are v19 and v18 on my arch machine and v18 on my ubuntu server

[norket]

the output in my arch machine is the next one:
=== System Info ===
OS: Linux_6.1.9-arch1-1_x64
Memory: 11.5gb (12450447360b)
Node Version: v18.13.0
=== 2Based2Wait Info ===
Current Commit Hash: efc301f
Package.json Version: 1.0.4
File Hashes:

• ./proxy.js: c07e18f
• ./package.json: 28705c6
• ./package-lock.json: afbf531
• ./util/chatty.js: 62f9255
• ./util/config.js: 40cb7f7
• ./util/downloader.js: 295c300
• ./util/logger.js: 351a46a
• ./util/mineflayer.js: 1b8a895
• ./util/ngrok.js: 2355f90
• ./util/notifier.js: 281beb8
• ./util/queue.js: 100c172
• ./util/schemas.js: 3891720
• ./scripts/debugFetch.js: c97a660
• ./scripts/processArchives.js: a46cfe4
• ./scripts/updateNgrokBinary.js: 4ce1999
• ./test/test-config.json: de34c55
• ./test/test.js: 4e96546
  Last Modified File: ./package-lock.json
  === Log Folders ===
• bridgeClientPackets (0 files/folders)
• chat (0 files/folders)
• error (0 files/folders)
• proxy (1 files/folders)
• serverPackets (0 files/folders)
  === Tests ===
  Config.json is Valid JSON5: true
  Passes Mocha Tests: true
  Is Mocha Installed: true

[unclamped]

Could you try to run the latest branch just in case? Download the repo's source code with the green button on the top of the file viewer, download the zip, extract it, and paste your 1.0.4 config file

[norket]

it lets me connect to the proxy, but doesnt works more than that, it becomes stuck in "checking queue position" and my client says that the server isnt responding, also the tab of 2b doesnt shows (i mean 2b queue tab), then after some time it just crashes with no error code (all this with the main repo)

[unclamped]

That's weird. Can you send your config.json file? Please make sure to remove all your sensitive information, such as your ngrok token and Discord webhooks.

[norket]

{
"account": {
"username": "account"
},

"proxy": {
	"whitelist": [ "account" ],
	"loopbackAddress": "0.0.0.0",
	"port": 25565
},

"discord": {
	"active": false,
	"webhook": {
		"spam": "YOUR DISCORD WEBHOOK",
		"livechat": "YOUR DISCORD WEBHOOK",
		"status": "YOUR DISCORD WEBHOOK"
	},
	"id": "id"
},

"queueThreshold": 21,

"server": {
	"host": "connect.2b2t.org",
	"port": 25565,
	"version": "1.12.2"
},

"mineflayer": {
	"active": false,
	"autoQueueMainInterval": 690,
	"killAura": {
		"interval": 0.69,
		"blacklist": [ "zombie_pigman", "enderman" ]
	},
	"autoEat": {
		"priority": "saturation",
		"startAt": 19,
		"bannedFood": [ "rotten_flesh", "pufferfish", "chorus_fruit", "poisonous_potato", "spider_eye" ]
	},
	"antiAfk": {
		"actions": [ "rotate", "swingArm" ],
		"fishing": false,
		"chatting": false,
		"chatMessages": [ "!pt", "!queue" ],
		"chatInterval": 690420
	}
},

    "waitForControllerBeforeConnect": true,

"experimental": {
	"disconnectIfNoController":{
	"active": true,
	"delay": 0
	}
},

"coordination": {
	"active": false,
	"path":  "./../"
}

}

[unclamped]

Pushed some updates to the repo, shouldn't do much but it's still good to be up to date. Could you share your log files from the log folder?
I think that there shouldn't be anything too important except for maybe coordinates in case you get to the normal server but try to give them a quick read before uploading