Argyl Posted March 5, 2019 Report Posted March 5, 2019 (edited) So just trying to figure out if I'm dumb or if something is up. I'm updating my bot manager and since update doesn't use steam-client anymore I can't use .bind() which was working. See my attached image. Basically client is still returning my own localhost IP. Not the proxy one I'm setting. Edited March 5, 2019 by Argyl Quote
Argyl Posted March 5, 2019 Author Report Posted March 5, 2019 (edited) So that was part of the issue. But now its not taking my proxies. Was connecting and logging in before and I tested them to make sure they are good to go. { "message": "bind EADDRNOTAVAIL 173.208.103.160:8800", "stack": "Error: bind EADDRNOTAVAIL 173.208.103.160:8800\n at internalConnect (net.js:824:18)\n at defaultTriggerAsyncIdScope (internal/async_hooks.js:299:19)\n at defaultTriggerAsyncIdScope (net.js:948 :9)\n at processTicksAndRejections (internal/process/next_tick.js:74:9)", "errno": "EADDRNOTAVAIL", "code": "EADDRNOTAVAIL", "syscall": "bind", "address": "173.208.103.160", "port": 8800 } That error crashes the process as well. Any ideas? Edited March 5, 2019 by Argyl Quote
Garik12 Posted March 5, 2019 Report Posted March 5, 2019 In my case, when I have updated steam-user to 4.2.0 or later, proxy setted by setHttpProxy stopped working fine, but when I rolled back to 3.21.1 it worked fine! But I need new version with proxy! Quote
Dr. McKay Posted March 6, 2019 Report Posted March 6, 2019 So that was part of the issue. But now its not taking my proxies. Was connecting and logging in before and I tested them to make sure they are good to go. { "message": "bind EADDRNOTAVAIL 173.208.103.160:8800", "stack": "Error: bind EADDRNOTAVAIL 173.208.103.160:8800\n at internalConnect (net.js:824:18)\n at defaultTriggerAsyncIdScope (internal/async_hooks.js:299:19)\n at defaultTriggerAsyncIdScope (net.js:948 :9)\n at processTicksAndRejections (internal/process/next_tick.js:74:9)", "errno": "EADDRNOTAVAIL", "code": "EADDRNOTAVAIL", "syscall": "bind", "address": "173.208.103.160", "port": 8800 } That error crashes the process as well. Any ideas? 173.208.103.160 is not an IP address assigned to any interface on your system. Is that a proxy IP? If so, just use the proxy option and don't set localAddress. In my case, when I have updated steam-user to 4.2.0 or later, proxy setted by setHttpProxy stopped working fine, but when I rolled back to 3.21.1 it worked fine! But I need new version with proxy! Please read the v4 release notes. Quote
Argyl Posted March 6, 2019 Author Report Posted March 6, 2019 Awesome, that did it. Thanks for that! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.