Jump to content


Photo
Question

Assigning proxy and new local address and port, client still showing public IP as my own.

node.js node-steam-user localaddress publicip

Best Answer Dr. McKay , 05 March 2019 - 09:38 PM

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.

Go to the full post


  • Please log in to reply
5 replies to this topic

#1 Argyl

Argyl

    Member

  • Member
  • PipPip
  • 21 posts

Posted 05 March 2019 - 01:46 AM

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.

 

 

 

440b5540cecc5e514d5acf595f9b0a37.png


Edited by Argyl, 05 March 2019 - 01:48 AM.


#2 Dr. McKay

Dr. McKay

    Developer

  • Administrator
  • 2,074 posts

Posted 05 March 2019 - 02:01 AM

Are you up to date?



#3 Argyl

Argyl

    Member

  • Member
  • PipPip
  • 21 posts

Posted 05 March 2019 - 06:43 AM

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 by Argyl, 05 March 2019 - 06:44 AM.


#4 Garik12

Garik12

    Newbie

  • Member
  • Pip
  • 1 posts

Posted 05 March 2019 - 04:14 PM

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!



#5 Dr. McKay

Dr. McKay

    Developer

  • Administrator
  • 2,074 posts

Posted 05 March 2019 - 09:38 PM   Best Answer

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.



#6 Argyl

Argyl

    Member

  • Member
  • PipPip
  • 21 posts

Posted 05 March 2019 - 09:56 PM

Awesome, that did it. Thanks for that!







Also tagged with one or more of these keywords: Question, node.js, node-steam-user, localaddress, publicip

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users