3urobeat Posted May 24 Report Share Posted May 24 (edited) Hey! I am unable to use the same proxies I use for steam-user with steam-session. My HTTP proxies do not use port 80 and as soon as I'm creating a LoginSession object using new SteamSession.LoginSession(SteamSession.EAuthTokenPlatformType.SteamClient, { httpProxy: "http://user:pass@ip:port" }) and calling startWithCredentials() this error fires: Error: connect ECONNREFUSED ::1:80 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '::1', port: 80, proxyConnecting: true } Is this intended behavior? The same proxy works without any problems with steam-user and steamcommunity. If I provide a socks proxy this problem does not occur. Sorry if I missed something in the documentation. Edit - Versions: node: 18.16.0 (but the same behavior appears on 19.something) steam-session: 1.2.2 OS: Arch Linux 6.3.3-arch1-1 steam-user (for comparison): 4.28.4 Edited May 24 by 3urobeat Added versions Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted May 25 Report Share Posted May 25 This was a bug. Run npm update and you should be set. 3urobeat 1 Quote Link to comment Share on other sites More sharing options...
3urobeat Posted May 25 Author Report Share Posted May 25 Oops, yeah you're right, even though I had the latest version installed, a simple 'npm update' fixed it. Sorry for bothering you ^^ Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted May 25 Report Share Posted May 25 No bother, I fixed the bug in response to this thread. It was in one of steam-session's dependencies which I maintain. 3urobeat 1 Quote Link to comment Share on other sites More sharing options...
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.