# OTAA ok, 12h later I get denied, reboot gateway --\> OK again ...!?

**URL:** <https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025>\
**Category:** End Devices (Nodes)\
**Created:** [May 3, 2016, 3:17pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025 "2016-05-03T15:17:35Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [May 13, 2016, 8:01am UTC](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025/7 "2016-05-13T08:01:10Z")

</div>

> [@lukas](#):
>
> ABP isn’t really working for me: once I disconnect my node from power, I have to regenerate the personalized device/keys. Maybe thats how it should be though.

Yes, [very much by design](http://staging.thethingsnetwork.org/wiki/LoRaWAN/Security#security-in-lorawan-and-ttn_frame-counters):

> […] you should realize that these frame counters reset to `0` every time the device restarts (when you flash the firmware or when you unplug it). As a result, The Things Network will block all messages from the device until the `FCntUp` becomes higher than the previous `FCntUp`. Therefore, you should re-register your device in the backend every time you reset it.

So, when using ABP for production, you should save the counters in non-volatile memory. For insecure debugging, one can [disable the check](https://www.thethingsnetwork.org/forum/t/abp-node-stopped-working-fixed-by-creating-new-abp-why/3200/7).

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025)._