# Recovering/Reauthorizing Decommissioned Device on Hosted Mender

**URL:** <https://hub.mender.io/t/recovering-reauthorizing-decommissioned-device-on-hosted-mender/2692>\
**Category:** General Discussions\
**Tags:** beaglebone-black, hosted\
**Created:** [October 20, 2020, 4:03am UTC](https://hub.mender.io/t/recovering-reauthorizing-decommissioned-device-on-hosted-mender/2692 "2020-10-20T04:03:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [October 20, 2020, 6:48am UTC](https://hub.mender.io/t/recovering-reauthorizing-decommissioned-device-on-hosted-mender/2692/2 "2020-10-20T06:48:21Z")

</div>

> [@poursteady](#):
>
> Is there a way to see a list of decommissioned devices within the [hosted.mender.io](http://hosted.mender.io) interface?

Do not think so. The idea of decommissioning is to remove any trace of that device (or actually an authorization set).

> Or a setting that would allow a device that was accidentally decommissioned to appear again?

A device which has been decommissioned should always come back in “Pending” state, should it try to connect again.

So the message you are seeing is correct,

```auto
Oct 20 03:45:08 ps157 mender[207]: time="2020-10-20T03:45:08Z" level=error msg="authorize failed: transient error: authorization request failed: (request_id: ): authentication request rejected server error message: dev auth: unauthorized" module=state

```

This should mean that you have an “Pending” authorization set on the server. It can be in two places, either under the “Pending” tab, or it could actually also be under “Devices” tab, as a new authorization set for an existing device. This is typically indicated by a small warning icon on the device.

---

_[View the full topic](https://hub.mender.io/t/recovering-reauthorizing-decommissioned-device-on-hosted-mender/2692)._
