All Activity
- Yesterday
-
Problem with logging in via qr code
THEzombiePL replied to THEzombiePL's topic in node-steam-session
I already found the reason and solved it, it was the fault that I use vpn and closing the dialog box with security questions worked for logging in with steamguard code but automatically rejects logging in with qr code. -
Problem with logging in via qr code
THEzombiePL replied to THEzombiePL's topic in node-steam-session
I accepted the login over the phone and closed the dialog box with security questions about the login sample questions: are you trying to pick up a free skin or are you trying to enter a tournament -
Did you decline the login on your mobile device? That's what I've seen cause FileNotFound.
- Last week
-
Problem with logging in via qr code
THEzombiePL replied to THEzombiePL's topic in node-steam-session
I used the official example to test but it doesn't work. I want to combine this with the steam-user library (which is working fine so far but I want to add qr login) -
THEzombiePL started following Problem with logging in via qr code
-
const { LoginSession, EAuthTokenPlatformType } = require('steam-session'); const qrcode = require('qrcode-terminal'); // We need to wrap everything in an async function since node <14.8 cannot use await in the top-level context main(); async function main() { // Create our LoginSession and start a QR login session. let session = new LoginSession(EAuthTokenPlatformType.MobileApp); session.loginTimeout = 120000; // timeout after 2 minutes let startResult = await session.startWithQR(); qrcode.generate(startResult.qrChallengeUrl, { small: true }); session.on('remoteInteraction', () => { console.log('Looks like you\'ve scanned the code! Now just approve the login.'); }); // No need to handle steamGuardMachineToken since it's only applicable to accounts using email Steam Guard, // and such accounts can't be authed using a QR code. session.on('authenticated', async () => { console.log('\nAuthenticated successfully! Printing your tokens now...'); console.log(`SteamID: ${session.steamID}`); console.log(`Account name: ${session.accountName}`); console.log(`Access token: ${session.accessToken}`); console.log(`Refresh token: ${session.refreshToken}`); // We can also get web cookies now that we've negotiated a session let webCookies = await session.getWebCookies(); console.log('Web session cookies:'); console.log(webCookies); }); session.on('timeout', () => { console.log('This login attempt has timed out.'); }); session.on('error', (err) => { // This should ordinarily not happen. This only happens in case there's some kind of unexpected error while // polling, e.g. the network connection goes down or Steam chokes on something. console.log(`ERROR: This login attempt has failed! ${err.message}`); }); } response: QRCODE... Looks like you've scanned the code! Now just approve the login. ERROR: This login attempt has failed! FileNotFound
-
THEzombiePL joined the community
-
Does anyone have a solution on how to download a manifest file that will be identical to the one in Steam or DepotDownloader?
- 4 replies
-
- node.js
- node-steam-user
-
(and 4 more)
Tagged with:
-
Michael_02 joined the community
-
Hi. i have a trading bot. here is my problem: context: i can use the them.escrowDays to check if they have their Mobile steam guard authenticator activated. if it's greater than 0, they don't (99 percent of the time, this method works for me) i show user the error, they activate their steam guard, then will come back in a few days. here is my question: is there a way for me to check how many days is left of their 15 days of trade hold? like if they activated their steam guard on may 10th and come back on may 20th, is there a way for me to tell them they have to come back in 5 days?
-
lllelkov joined the community
-
I figured it out but how to i keep the eya token alive for more than 200 days
- 2 replies
-
- internet cafe
- help
-
(and 3 more)
Tagged with:
-
Pip reacted to a post in a topic: Error 26 (eruslt=26) - unable to send offers via BOT
-
Error 26 (eruslt=26) - unable to send offers via BOT
Dr. McKay replied to Pip's topic in node-steam-tradeoffer-manager
Ignore any id and assetid properties in the description object when you merge it onto the asset object. -
Error 26 (eruslt=26) - unable to send offers via BOT
Pip replied to Pip's topic in node-steam-tradeoffer-manager
It seems that I have to manually repair Inventory object that is being passed on to a function creating trade offer. AssetID is being registered once the trade offer is successfully completed. I can collect that data, add them to new columns: sm_product & market_items. Afterwards, send this parameter each time to the BOT so it will replace this parameter in the Inventory object before creating a trade. Is that a proper solution? -
Error 26 (eruslt=26) - unable to send offers via BOT
Pip replied to Pip's topic in node-steam-tradeoffer-manager
Hello, There is indeed a problem with inconsistency of IDs and AssetIDs in the inventory. How can I solve that? That is the reason why I get error 26 while sending trade offers. https://i.postimg.cc/G3m4XFxb/assetidsproblem.png -
Error 26 (eruslt=26) - unable to send offers via BOT
Dr. McKay replied to Pip's topic in node-steam-tradeoffer-manager
That error code indicates that your item ID is wrong or doesn't exist. Some people have reported that item descriptions now contain invalid asset IDs which you need to filter out if you're parsing inventories yourself. -
Btw can you recomend a good setup for fully hosting refresh token server topt you know we have a server
- 2 replies
-
- internet cafe
- help
-
(and 3 more)
Tagged with:
-
herroro4 joined the community
-
Im trying to generate eya tokens for a internet cafe but idk how to use this
- 2 replies
-
- internet cafe
- help
-
(and 3 more)
Tagged with:
-
Pip started following Error 26 (eruslt=26) - unable to send offers via BOT
-
Hello, I use your BOT. I have got over 100 Steam accounts with a lot of items. All of the items are being sent via your BOT. Since a few days, exactly since 05.03.2025, 00:20 (European time) I am getting an "26" error at a lot of my accounts. Items are not being sent. 2025-03-05T00:27:44.588Z - error: Error creating trade offer orderId=XXX, botName=XXX, eresult=26, message=There was an error sending your trade offer. Please try again later. (26), skin=P2000 | Lifted Spirits (Field-Tested), steamId=[U:1:XXX], user_id=XXX, tradeurl=https://steamcommunity.com/tradeoffer/new/?partner=XXX&token=XXX I am aware of that: https://steamerrors.com/26 The problem is that: I have got many items at my inventory, for example 10 x "P2000 | Lifted Spirits (Field-Tested)" item. My inventory is not full. It is not banned or limited. Items are being present at my account, they are not being sent in other trade offers meanwhile. I am able to send items manually, without using a BOT. Some items, on the same Steam account, are being sent without a problem, while others generate "26" error". I highly doubt that it is some kind of a shadow-ban imposed by Steam. I cannot find any logic in this error. I have tried to send random items, with other assetIDs but the same problem occurs. I have tried to add funds to Steam accounts, play CS2 game, buy games. Nothing helps. Did Steam made some changes in the Steam API in the last few days?
-
I looked into this issue and found out that it's not a problem with the proxy provider. I was testing steam-user functionality in Deno, which is not fully compatible with Node.js—especially with https-proxy-agent, which steam-user uses under the hood. import axios from 'axios'; import { HttpsProxyAgent } from 'https-proxy-agent'; const httpsAgent = new HttpsProxyAgent('PROXY_URL_HERE'); const instance = axios.create({ httpsAgent, timeout: 15000 }); const res = await instance.get('https://steamcommunity.com'); console.log(res.data, res.status); For instance, this code works perfectly fine in Node.js, whereas in the Deno runtime, it throws an error. I guess I'll have to stick with Node.js for now.
-
Unable to Login (stuck in a loop most likley)
Hsn_CODES replied to Hsn_CODES's topic in node-steam-user
2025-03-09T13:20:45.341Z - Error reading file machineAuthToken.sinstv18.txt: ENOENT: no such file or directory, open 'C:\Users\hassaan\AppData\Local\doctormckay\node-steamuser\machineAuthToken.sinstv18.txt' 2025-03-09T13:20:45.550Z - Error reading file machineAuthToken.sinstv18.txt: ENOENT: no such file or directory, open 'C:\Users\hassaan\AppData\Local\doctormckay\node-steamuser\machineAuthToken.sinstv18.txt' 2025-03-09T13:20:46.147Z - API GET request to https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v0001/?format=vdf&cellid=0: 200 2025-03-09T13:20:46.150Z - Randomly chose websockets server cmp2-iad1.steamserver.net:27020 (load = 13, wtd_load = 5.23279571533203125) 2025-03-09T13:20:46.150Z - [W1] Connecting to WebSocket CM cmp2-iad1.steamserver.net:27020 2025-03-09T13:20:46.279Z - API GET request to https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v0001/?format=vdf&cellid=0: 200 2025-03-09T13:20:46.282Z - Randomly chose netfilter server 162.254.195.66:27017 (load = 17, wtd_load = 9.83317804336547852) 2025-03-09T13:20:46.282Z - [T1] Connecting to TCP CM: 162.254.195.66:27017 2025-03-09T13:20:46.588Z - [T1] TCP connection established 2025-03-09T13:20:46.872Z - [T1] Handled message: ChannelEncryptRequest 2025-03-09T13:20:46.873Z - Channel encrypt request: protocol 1, universe 1, nonce 849637bb018ea6c79d641c5b91c8fcd8, 0 remaining bytes 2025-03-09T13:20:46.874Z - Sending message: ChannelEncryptResponse 2025-03-09T13:20:47.081Z - [W1] WebSocket connection success; now logging in 2025-03-09T13:20:47.082Z - Logging on with account name and password; fetching a new refresh token 2025-03-09T13:20:47.084Z - Sending message: ClientHello 2025-03-09T13:20:47.090Z - Sending message: Authentication.GetPasswordRSAPublicKey#1 2025-03-09T13:20:47.091Z - steam-session startWithCredentials exception 2025-03-09T13:20:47.091Z - Handle logon response (ServiceUnavailable) 2025-03-09T13:20:47.091Z - Log on response: ServiceUnavailable 2025-03-09T13:20:47.092Z - Disconnecting without sending logoff 2025-03-09T13:20:47.092Z - [W1] Ending connection and removing all listeners 2025-03-09T13:20:47.092Z - [EBO] Queueing exponential backoff "logOn" with timeout 1000 Even after changing my internet i am getting the same debug logs. -
Unable to Login (stuck in a loop most likley)
Dr. McKay replied to Hsn_CODES's topic in node-steam-user
You likely have some kind of network issue. Add this and see what's happening: client.on('debug', console.log); -
I've been having issues logging in with steam-user while using proxies. Can anyone recommend a reliable proxy provider that works well with steam-user, especially for websocket connections?
- Earlier
-
Hsn_CODES joined the community
-
const SteamUser = require('steam-user'); // const SteamTotp = require('steam-totp'); const client = new SteamUser(); const logOnOptions = { accountName: '---', password: '---', // twoFactorCode: SteamTotp.generateAuthCode('---') }; client.logOn(logOnOptions); client.on('loggedOn', () => { console.log('Logged into Steam'); client.setPersona(SteamUser.EPersonaState.Away); console.log('STATUS = AWAY'); client.gamesPlayed(440); }); even though I am using an example code, the code isn't giving any output. I tried debugging the code and it's stuck in a loop, It keeps going through all the funcitons, again and again in the file named "09-logon.js". i tried both using and account without any 2fa and with 2fa also providing the secret code but i get no output. any help?
-
beanny joined the community
-
@Dr. McKayif the login history shows all the logins form france then how come that the auth device location is diff can u help me narrow it down a bit? Also is there a way to change the device id everytime we call log on?
-
thats the only steam related thing i do client form steam user and steam community and passing that client over to steam trade offer manager there cant be a mistake. i will share some results after testing something as well but u see all the logins are from the proxy location how come th auth device location is diff the issue comes down to steam user
-
Looks fine to me, you probably have a mistake elsewhere in your code.