- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Brute force attempt detected.
I received a [Brute force attempt detected. Please wait 5 minutes and try again.] when attempting to claim products. What does this mean and why does it occur?
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for the late reply. It happened only once and it was just when I had broken up one Organization into two different organizations un-claiming some licenses from one organization and then re-claiming them again in the newly created organization. (Of course, it required Meraki to help transfer the licenses in the backend.)
I've closely watched the even logs for further/similar possible worrying events, but none were discovered so I'll mark this up as a one-time move of licenses from one organization to another glitch!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would call support and see what is going on, perhaps your Meraki dashboard login has been compromised. If you don't already I suggets you use 2FA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@wbenton, did you receive an error when trying to claim the products so you kept trying? I've had that happen to me before when attempting to claim products and my order number/serial number wouldn't work. Typically, I just work with my Meraki rep and this gets resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for the late reply. It happened only once and it was just when I had broken up one Organization into two different organizations un-claiming some licenses from one organization and then re-claiming them again in the newly created organization. (Of course, it required Meraki to help transfer the licenses in the backend.)
I've closely watched the even logs for further/similar possible worrying events, but none were discovered so I'll mark this up as a one-time move of licenses from one organization to another glitch!
