You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Some mods could not be installed
Installation of some mods failed. Review the errors below:
Too many incorrect login attempts. Please try again later (no sooner than 30 minutes after last attempt)."
The above error message persists through restarting the docker instance, and is present even before I attempt to update any mods.
The only problem is, we can login elsewhere, and the UI isn't actually generating any Steam Guard emails either any more; It's almost like the Server Manager is stuck in this state and can no longer contact Steam to log in. I'll attach some logs in my next comments.
The text was updated successfully, but these errors were encountered:
https://steamcommunity.com/discussions/forum/14/282992646978516395/ according to this discussion, it appears to be an issue with incorrect login information, but I've tested it on Steam's website, it works just fine. mr-guard/dayz-server-manager#23 appears to be downloading too many mods at once, though I don't know how this dayz-server-manager works. By issue 48, linked at the bottom, it appears each mod downloaded is a login, so too many mods is causing rate limiting? armaservermanager.log
Lexicon-Prime
changed the title
Server Manager is unable to login to Steam at all
Server Manager is unable to download mods whatsoever due to being Rate Limited
Feb 8, 2024
"Some mods could not be installed
Installation of some mods failed. Review the errors below:
Too many incorrect login attempts. Please try again later (no sooner than 30 minutes after last attempt)."
The above error message persists through restarting the docker instance, and is present even before I attempt to update any mods.
The only problem is, we can login elsewhere, and the UI isn't actually generating any Steam Guard emails either any more; It's almost like the Server Manager is stuck in this state and can no longer contact Steam to log in. I'll attach some logs in my next comments.
The text was updated successfully, but these errors were encountered: