Closed acuifex closed 4 years ago
Sometimes it works and sometimes it doesn't?
I assume this is because of Steam's differing connection protocols. You can either connect to Steam using TCP or WebSocket, I assume your proxy is blocking TCP connections but allows WebSockets.
There are ways to force what type of connection protocol to use but this is not implemented at the moment. I will add a new optional config option to force protocol in the future.
It worked something like 20 times for me at the end of commenting a few times. you're probably right. There are some features from nord that could have some effect on that:
"features": {
"ikev2": false,
"openvpn_udp": false,
"openvpn_tcp": false,
"socks": false,
"proxy": false,
"pptp": false,
"l2tp": false,
"openvpn_xor_udp": true,
"openvpn_xor_tcp": true,
"proxy_cybersec": false,
"proxy_ssl": false,
"proxy_ssl_cybersec": false,
"ikev2_v6": false,
"openvpn_udp_v6": false,
"openvpn_tcp_v6": false,
"wireguard_udp": false,
"openvpn_udp_tls_crypt": false,
"openvpn_tcp_tls_crypt": false,
"openvpn_dedicated_udp": false,
"openvpn_dedicated_tcp": false,
"skylark": false
}
edit: that is just random server. i obviously use proxy ssl ones.
Potentially fixed in 0fb0418ce170c104c5026984af866d6d1f56c800?
Please update the bot and update your config with the new protocol
option, set it to WebSocket
then try again. Report back if it works or not.
With tcp i get 405 and with websocket:
[accountname] Failed to login and due to proxy timeout (20/20) {
name: 'Error',
message: 'Failed to log in within given 60000ms',
stack: 'Error: Failed to log in within given 60000ms\n' +
' at Timeout._onTimeout (/home/acuifex/Programs/csgo-commend-bot/helpers/account.js:60:12)\n' +
' at listOnTimeout (internal/timers.js:549:17)\n' +
' at processTimers (internal/timers.js:492:7)'
}
config:
"commend": {
"friendly": 20,
"teaching": 20,
"leader": 20
},
"report": {
"aimbot": 10,
"wallhack": 10,
"speedhack": 10,
"teamharm": 10,
"abusive": 10
},
"account": {
"username": "1",
"password": "2",
"sharedSecret": ""
},
"fetcher": {
"username": "2",
"password": "1",
"sharedSecret": "",
"maxTries": 10,
"tryDelay": 2500,
"askSteamGuard": false
},
"proxy": {
"enabled": true,
"file": "proxies.txt",
"switchProxyEveryXaccounts": 1
},
"type": "COMMEND",
"method": "LOGIN",
"target": "https://steamcommunity.com/profiles/acc/",
"serverID": "[A:1:3341319169:15188]",
"matchID": "0",
"perChunk": 20,
"betweenChunks": 1000,
"cooldown": 28800000,
"showCommends": true,
"autoReportOnMatchEnd": false,
"switchServerAfterChunks": 5,
"protocol": "WebSocket",
"steamWebAPIKey": "f",
"disableUpdateCheck": false
}
Last try, update again and set protocol
to WebCompatibility
still same as websocket. maybe nord isn't good for steam or i search for wrong servers. also
"WEBSOCKET": 2,
"WEBCOMPATABILITY": 2
That is on purpose. WebCompatibility forces WebSocket mode
Yeah I am out of ideas, I assume Steam blocked some NordVPN IP's
i can provide you some public nord accs if you want to test at some point. telegram @acuifex or gitter same nickname.
Not gonna solve anything. Just use a other/better proxies.
Detailed bug description i'm getting 405 when using nordvpn as a proxy, but sometimes it works a few times for some reason. i write my proxies like this:
i censored account names because it might be a sensitive info.
Error
Config
Version
v12.16.3
(You can find this usingnode -v
)2.9.0
(You can find this in yourpackage.json
file underversion
)