# OTAA accept not received when in reach of multiple gateways

**URL:** <https://www.thethingsnetwork.org/forum/t/otaa-accept-not-received-when-in-reach-of-multiple-gateways/32074>\
**Category:** Gateways\
**Created:** [November 24, 2019, 7:12pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-accept-not-received-when-in-reach-of-multiple-gateways/32074 "2019-11-24T19:12:35Z")\
**Posts on this page:** 1\
**Showing post:** 31

<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:** [December 1, 2019, 1:58pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-accept-not-received-when-in-reach-of-multiple-gateways/32074/31 "2019-12-01T13:58:26Z")

</div>

> [@Grillbaer](#):
>
> the join-JSONs on MQTT looked quite complete except for the one case, where there was a nonce error message

Then I’d assume that you’ll get all errors, including [Activation not valid - no gateways available](https://www.thethingsnetwork.org/forum/t/activation-not-valid-no-gateways-available/5649) when applicable.

Yet another aside: if your tests are getting you a lot of “Activation DevNonce not valid: already used” then this might help:

> [@OTAA shows "Activation DevNonce not valid: already used"](https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079/13):
>
> A workaround from @htdvisser on Slack, if you really need to clear the nonces that TTN has stored:
> 
> > The backend clears the DevNonces when you change the AppKey, so if this is a problem, you can just change the AppKey to something else and then change it back

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-accept-not-received-when-in-reach-of-multiple-gateways/32074)._