Couldn't log in bot0 after 2 attempt(s). Error: AccessDenied (15)

[memendes123]

[ERROR] Couldn't log in bot0 after 2 attempt(s). Error: AccessDenied (15)

[ERROR] Aborting because the first bot account always needs to be logged in! Please correct what caused the error and try again.

I didn't change anything, it just stopped working, how do I fix it?

[3urobeat]

Hey, thanks for opening an issue!
I'm not particularly sure why Steam is blocking your login request as AccessDenied is pretty vague.
It might be that your IP received a cooldown, the account itself or maybe even Steam had/has some Server problems right now.
You could try changing your IP or just waiting a bit and trying again later.

[memendes123]

hello, i teyed with vpn different login and still with same error

3urobeat @.***> escreveu no dia quarta, 3/05/2023 à(s) 22:40:

Hey, thanks for opening an issue! I'm not particularly sure why Steam is blocking your login request as AccessDenied is pretty vague. It might be that your IP received a cooldown, the account itself or maybe even Steam had/has some Server problems right now. You could try changing your IP or just waiting a bit and trying again later.

— Reply to this email directly, view it on GitHub https://github.com/HerrEurobeat/steam-comment-service-bot/issues/167#issuecomment-1533788963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUDUWOHIVQ2NXRT4QX4YHULXELGFLANCNFSM6AAAAAAXU63SBU . You are receiving this because you authored the thread.Message ID: @.***>

-- Helder Alves

Profissional de Gestão +351 926725627 <+351+926725627> @.*** Rua do tanque nº96 Povoação , 4820-664 São-Gens, Fafe [image: facebook] https://www.facebook.com/helderalves123/ [image: linkedin] https://www.linkedin.com/in/helder-a-b27a5b141/ [image: instagram] https://www.instagram.com/helderalves1000/

[3urobeat]

Steam appears to have some issues right now as you can see here: https://steamstat.us/
My bot also fails to log in properly right now, however for a different reason. I think these issues are related and you should try again in a few minutes.

[memendes123]

still with same problems, will try in the morning

3urobeat @.***> escreveu no dia quarta, 3/05/2023 à(s) 22:47:

Steam appears to have some issues right now as you can see here: https://steamstat.us/ My bot also fails to log in properly right now, however for a different reason. I think these issues are related and you should try again in a few minutes.

— Reply to this email directly, view it on GitHub https://github.com/HerrEurobeat/steam-comment-service-bot/issues/167#issuecomment-1533796548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUDUWODUUU772MAYWPLFGO3XELHAFANCNFSM6AAAAAAXU63SBU . You are receiving this because you authored the thread.Message ID: @.***>

-- Helder Alves

Profissional de Gestão +351 926725627 <+351+926725627> @.*** Rua do tanque nº96 Povoação , 4820-664 São-Gens, Fafe [image: facebook] https://www.facebook.com/helderalves123/ [image: linkedin] https://www.linkedin.com/in/helder-a-b27a5b141/ [image: instagram] https://www.instagram.com/helderalves1000/

[3urobeat]

For me logging in works fine again.
Depending on whether your bot logs in using the new token system or the old sentry file system, it might be worth trying to delete either the tokens.db or the associated .bin sentry file.

If you are using the bot for the first time you can skip reading this, you'll automatically use the new system:
Check your output.txt file, it should tell you right above the error you posted at first which system is being used.
It will either say Found valid token until '2023-11-30 16:38:27 (GMT time)' in tokens.db! Logging in with it to reuse session... when using the new system or No token found in tokens.db. Logging in with credentials to get a new session... when using the old system.

When using the new system (which will become mandatory in 2.13):
Delete your tokens.db file, located in ./src/data/ inside the bot folder. Start the bot again, it should log in and ask for your SteamGuard code again.

When using the old system it get's a bit more complicated:
Depending on which OS you use the file will be in a different spot. You can find the folder for your OS listed here: https://github.com/DoctorMcKay/node-steam-user#datadirectory
Open the folder and delete the corresponding .bin file for the affected account. It will have the same name as the username of the account in question.

Please let me know if this changed something for you. I sadly have no other idea otherwise as this is a Steam related issue and not caused by the bot. I've found a few threads on the internet with the same error but none really had helpful answers. Steam also doesn't provide more information about the errors they throw which is sad.

[memendes123]

Thanks, it worked.

3urobeat @.***> escreveu no dia quinta, 4/05/2023 à(s) 09:59:

For me logging in works fine again. Depending on whether your bot logs in using the new token system or the old sentry file system, it might be worth trying to delete either the tokens.db or the associated .bin sentry file.

If you are using the bot for the first time you can skip reading this, you'll automatically use the new system: Check your output.txt file, it should tell you right above the error you posted at first which system is being used. It will either say Found valid token until '2023-11-30 16:38:27 (GMT time)' in tokens.db! Logging in with it to reuse session... when using the new system or No token found in tokens.db. Logging in with credentials to get a new session... when using the old system.

When using the new system (which will become mandatory in 2.13): Delete your tokens.db file, located in ./src/data/ inside the bot folder. Start the bot again, it should log in and ask for your SteamGuard code again.

When using the old system it get's a bit more complicated: Depending on which OS you use the file will be in a different spot. You can find the folder for your OS listed here: https://github.com/DoctorMcKay/node-steam-user#datadirectory Open the folder and delete the corresponding .bin file for the affected account. It will have the same name as the username of the account in question.

Please let me know if this changed something for you. I sadly have no other idea otherwise as this is a Steam related issue and not caused by the bot. I've found a few threads on the internet with the same error but none really had helpful answers. Steam also doesn't provide more information about the errors they throw which is sad.

— Reply to this email directly, view it on GitHub https://github.com/HerrEurobeat/steam-comment-service-bot/issues/167#issuecomment-1534343012, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUDUWOHELQ54B7HEQN7JMTTXENVVVANCNFSM6AAAAAAXU63SBU . You are receiving this because you authored the thread.Message ID: @.***>

-- Helder Alves

Profissional de Gestão +351 926725627 <+351+926725627> @.*** Rua do tanque nº96 Povoação , 4820-664 São-Gens, Fafe [image: facebook] https://www.facebook.com/helderalves123/ [image: linkedin] https://www.linkedin.com/in/helder-a-b27a5b141/ [image: instagram] https://www.instagram.com/helderalves1000/

[3urobeat]

That's great to hear! I'm going to close this issue then.
If you have any other questions always feel free to open another issue! :)