# log in attempts

**URL:** <https://forums.digi.com/t/log-in-attempts/6477>\
**Category:** Digi CM & Passport\
**Created:** [September 28, 2005, 4:16pm UTC](https://forums.digi.com/t/log-in-attempts/6477 "2005-09-28T16:16:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shendrickson](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shendrickson](https://forums.digi.com/u/shendrickson)\
**Post date:** [September 28, 2005, 4:16pm UTC](https://forums.digi.com/t/log-in-attempts/6477/1 "2005-09-28T16:16:03Z")

</div>

We have recently upgraded one of our cm32 to v1.7.0.1 Ever since the upgrade we have been experiencing issues with user logins. It appears that if the password is incorrectly typed after about 3 attempts, it locks you out of the device. I have not been able to find a configurable parameter to eliminate this issue. Any ideas? We didn’t have this issue when running on a much older version.

Thanks

Stacy

---

<div class="post-metadata">

**Author:** ![michaelt](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/michaelt/32/92_2.png) [@michaelt](https://forums.digi.com/u/michaelt)\
**Post date:** [September 28, 2005, 4:19pm UTC](https://forums.digi.com/t/log-in-attempts/6477/2 "2005-09-28T16:19:10Z")

</div>

Since you upgraded from a “much older version” to the 1.7.0.1, I’d recommend factory defaulting your Digi CM. A lot of options/features were changed, improved, or added, and that’s probably the source of the problems you’re seeing. If you still have problems after a factory default on the new firmware, please call tech support and open a ticket.

---

<div class="post-metadata">

**Author:** ![shendrickson](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shendrickson](https://forums.digi.com/u/shendrickson)\
**Post date:** [September 29, 2005, 3:14pm UTC](https://forums.digi.com/t/log-in-attempts/6477/3 "2005-09-29T15:14:19Z")

</div>

When I performed the upgrade, because it was from such an old version if factory defaulted itself and I had to reconfigure from scratch. I will go ahead and open a ticket to research the issue.
