# \#deviceauth

**URL:** https://hub.mender.io/tag/deviceauth/208.md

[Latest](https://hub.mender.io/latest.md) · [Categories](https://hub.mender.io/categories.md) · [Tags](https://hub.mender.io/tags.md)

---

## [Not able to receive the Device Authentication Token via Device API. signature verification failed](https://hub.mender.io/t/not-able-to-receive-the-device-authentication-token-via-device-api-signature-verification-failed/7705)

<div class="topic-metadata">

**Author:** [@grasshopper](https://hub.mender.io/u/grasshopper)\
**Replies:** 4\
**Last updated:** [May 5, 2025, 9:09am UTC](https://hub.mender.io/t/not-able-to-receive-the-device-authentication-token-via-device-api-signature-verification-failed/7705 "2025-05-05T09:09:13Z")

</div>

I am using hosted Mender with a virtual qemu device. I am calling the device authentication API endpoint and try to receive the Device Token as a response. curl \\ -H "Content-Type: application/json" \\ -H "X-MEN…

---

## [Cannot add device after decommissioning a device on hosted mender](https://hub.mender.io/t/cannot-add-device-after-decommissioning-a-device-on-hosted-mender/6328)

<div class="topic-metadata">

**Author:** [@Shaked](https://hub.mender.io/u/Shaked)\
**Replies:** 4\
**Last updated:** [February 2, 2024, 9:32am UTC](https://hub.mender.io/t/cannot-add-device-after-decommissioning-a-device-on-hosted-mender/6328 "2024-02-02T09:32:43Z")

</div>

Hi, I have been experiencing a new error in the last few weeks which I haven’t seen before. Some information about my setup I have around 120 IoT devices connected to https://hosted.mender.io/ I have an automated proc…

---

## [Mender-stress-test-client corrupted the MongoDB](https://hub.mender.io/t/mender-stress-test-client-corrupted-the-mongodb/5996)

<div class="topic-metadata">

**Author:** [@kostiantyn.nosachov](https://hub.mender.io/u/kostiantyn.nosachov)\
**Replies:** 3\
**Last updated:** [July 13, 2023, 12:51pm UTC](https://hub.mender.io/t/mender-stress-test-client-corrupted-the-mongodb/5996 "2023-07-13T12:51:46Z")

</div>

Hey there Community! We have an OpenSource Mender 3.4 installed as a Dev environment. It was deployed by Docker-Compose. 2vCPU 1GB. t3micro instance. After some time we decided we have to do a load tests and our choice…

---

## [Devices showing in pending without pending device auth set](https://hub.mender.io/t/devices-showing-in-pending-without-pending-device-auth-set/5804)

<div class="topic-metadata">

**Author:** [@dpostorivo](https://hub.mender.io/u/dpostorivo)\
**Replies:** 2\
**Last updated:** [May 9, 2023, 5:05pm UTC](https://hub.mender.io/t/devices-showing-in-pending-without-pending-device-auth-set/5804 "2023-05-09T17:05:15Z")

</div>

Running a self hosted mender 2.7, over the last few days we’re seeing pending devices with no auth sets. We reset a device that was already accepted to give it a new authset, but it also does not show up so it is unable …

---

## [Device can't connect to hosted server](https://hub.mender.io/t/device-cant-connect-to-hosted-server/5686)

<div class="topic-metadata">

**Author:** [@mister\_kanister](https://hub.mender.io/u/mister_kanister)\
**Replies:** 3\
**Last updated:** [March 27, 2023, 4:52pm UTC](https://hub.mender.io/t/device-cant-connect-to-hosted-server/5686 "2023-03-27T16:52:41Z")

</div>

Hello Friends! I configured my mender client on my SBC and authorized it in the dashboard. However, I get the authorization errors and the device can’t update its inventory. I don’t use systemd. There is no startup scri…

---

## [Upgrading from Mender 2.0.1 to 2.7.1 - devices not shown in GUI (but 2.6.1 ok)](https://hub.mender.io/t/upgrading-from-mender-2-0-1-to-2-7-1-devices-not-shown-in-gui-but-2-6-1-ok/4163)

<div class="topic-metadata">

**Author:** [@Suppo](https://hub.mender.io/u/Suppo)\
**Replies:** 1\
**Last updated:** [October 8, 2021, 10:17am UTC](https://hub.mender.io/t/upgrading-from-mender-2-0-1-to-2-7-1-devices-not-shown-in-gui-but-2-6-1-ok/4163 "2021-10-08T10:17:20Z")

</div>

Recently we upgraded our old (2.0.1) self-hosted mender server from version to 2.6.1 successfully. The reason we couldn’t go to 2.7.x branch was that we just were unable make the GUI show us all the previously registered…
