# Mender-Client failed to update deployment status

**URL:** <https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858>\
**Category:** General Discussions\
**Created:** [June 30, 2025, 8:07am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858 "2025-06-30T08:07:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [June 30, 2025, 8:07am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/1 "2025-06-30T08:07:07Z")

</div>

Hi I’ve hosted a mender server on aws ec2 which seems to function properly, and i have a ubuntu24 machine on which i installed mender client(v5) through `apt install mender-client4`. The client can be properly registered to my mender server, but when i tried to deploy an artifact, the client reported the below error

```auto

Jun 30 08:01:14 konnexthome mender-update[810890]: record_id=18 severity=info time="2025-Jun-30 08:01:14.570687" name="Global" msg="Sending status update to server"
Jun 30 08:01:14 konnexthome mender-update[810890]: record_id=19 severity=error time="2025-Jun-30 08:01:14.860295" name="Global" msg="Request to push status data failed: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "
Jun 30 08:01:14 konnexthome mender-update[810890]: record_id=20 severity=error time="2025-Jun-30 08:01:14.860475" name="Global" msg="Could not send deployment status: bad version: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=21 severity=info time="2025-Jun-30 08:01:15.142817" name="Global" msg="Installing artifact..."
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=22 severity=info time="2025-Jun-30 08:01:15.197851" name="Global" msg="Sending status update to server"
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=23 severity=error time="2025-Jun-30 08:01:15.200322" name="Global" msg="Request to push status data failed: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=24 severity=error time="2025-Jun-30 08:01:15.200493" name="Global" msg="Could not send deployment status: bad version: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "

```

I’ve tried to use the same client installation process and artifact on the hosted mender, and the artifact can be properly deployed without reporting this error. The server version is update-to-date(5.0.1), and it is installed using the k3s process. I’m kinda stuck on this, could you please kindly provide me with some advicie in regards to this issue? Really appreciate that.

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 1, 2025, 12:30am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/2 "2025-07-01T00:30:23Z")

</div>

I tried to downgrade my mender client to v3.5 and the BAD VERSION issue didn’t occur. I could see related issues in the release notes ( \* Fix download failure to always do a proper cancellation and cleanup of internal HTTP stuctures to avoid breaking future HTTP requests. Fixes `bad_version` error. ([MEN-7810](https://northerntech.atlassian.net/browse/MEN-7810), is it possible that the issue still exists?

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [July 2, 2025, 8:41am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/3 "2025-07-02T08:41:58Z")

</div>

Hi @nicktech,

It’s not a problem which we are aware of immediately. Possibly long shot, does it also persist when trying it on the Hosted Mender instance?

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 3, 2025, 1:25am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/5 "2025-07-03T01:25:50Z")

</div>

[Deployment status update failing](https://hub.mender.io/t/deployment-status-update-failing/7822), here is a recent post with the same issue

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 3, 2025, 1:26am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/6 "2025-07-03T01:26:13Z")

</div>

It does not occur in hosted mender or mender-client(v3.5), but persists across mender client v4-v5. Mender-updated service kept reporting error when communicating with mender-authd service.

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [July 3, 2025, 5:23pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/7 "2025-07-03T17:23:17Z")

</div>

Hi @nicktech,

No idea then, maybe @robgio has a pointer on how to debug the issue server side then.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 2:33am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/8 "2025-07-04T02:33:44Z")

</div>

ok, appreciate that. I’ll stick to mender-client v3 for now.

---

<div class="post-metadata">

**Author:** ![robgio](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/robgio/32/1760_2.png) [@robgio](https://hub.mender.io/u/robgio)\
**Post date:** [July 4, 2025, 4:33am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/9 "2025-07-04T04:33:37Z")

</div>

Hi @nicktech ,  
in your Mender Server setup, could you please check the Deployment service logs?

Something like

```auto
kubectl logs <deployment service pod> --namespace <your namespace>

```

Additionally, which Mender Server version are you using? With which helm chart version? Are you using the `storage_proxy` feature?

Thanks

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 9:12am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/10 "2025-07-04T09:12:54Z")

</div>

Hi,

- mender server version is v4.0.1, the latest version i suppose
- helm chart version is v3.18.3
- I’ve actually disabled the `storage_proxy` feature. When the feature is enabled, artifacts could not be properly downloaded from my mender website. (All artifacts are stored in S3)

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 9:14am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/11 "2025-07-04T09:14:26Z")

</div>

AS for the logs, i could not find much helpful information, are there anything that I should pay special attention to? Thanks a lot for your assistance.

---

<div class="post-metadata">

**Author:** ![robgio](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/robgio/32/1760_2.png) [@robgio](https://hub.mender.io/u/robgio)\
**Post date:** [July 4, 2025, 9:34am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/12 "2025-07-04T09:34:17Z")

</div>

Hi @nicktech ,  
for the exact Mender Server version you can look at the image tags of the Mender Services:

```auto
kubectl get deploy -o yaml --namespace <mender namespace> | grep -i image: 

```

You mentioned the helm chart version v3.18.3, but I guess that’s the version of the helm as a package. Could you please check which Mender Helm Chart version did you installed?

```auto
helm ls

```

For a complete list you can check:

```auto
helm search repo mender/mender --versions

```

as for

> - I’ve actually disabled the `storage_proxy` feature. When the feature is enabled, artifacts could not be properly downloaded from my mender website. (All artifacts are stored in S3)

This raises a warning to me: can you please share your helm chart values files, after removing all the sensitive secrets?

Thanks

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 10:13am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/13 "2025-07-04T10:13:51Z")

</div>

Thanks for the quick reply and my apologies for the inconcise information.

As for mender service versions, here is the full list of services that I’ve deployed

```bash
ubuntu@ip-172-31-7-3:~$ kubectl get deploy -o yaml -n default | grep -i image
          image: docker.io/traefik:3.4.1
          image: docker.io/mendersoftware/create-artifact-worker:v4.0.1
          - name: DEPLOYMENTS_STORAGE_MAX_IMAGE_SIZE
          image: docker.io/mendersoftware/deployments:v4.0.1
          image: docker.io/mendersoftware/deviceauth:v4.0.1
          image: docker.io/mendersoftware/deviceconfig:v4.0.1
          image: docker.io/mendersoftware/deviceconnect:v4.0.1
          image: docker.io/mendersoftware/gui:v4.0.1
          image: docker.io/mendersoftware/inventory:v4.0.1
          image: docker.io/mendersoftware/iot-manager:v4.0.1
          image: natsio/nats-box:0.13.8
          image: docker.io/mendersoftware/useradm:v4.0.1
          image: docker.io/mendersoftware/workflows:v4.0.1
          image: docker.io/mendersoftware/workflows:v4.0.1

```

As for the helm chart version

```bash
ubuntu@ip-172-31-7-3:~$ helm ls
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
mender default 7 2025-07-01 07:18:50.835959514 +0000 UTC deployed mender-6.6.1 v4.0.1

```

And here is my `mender-values.yaml` file. It basically strictly follows the default and recommended setup process in the mender docs server installation section, except that I’ve disabled `storage_proxy` to enable artifact download.

Moreover, I’ve attached a middle ware with some configurations about traefik so that I could upload artifacts with size more than 300mb. This can be seen in the ingress annotation part `traefik.ingress.kubernets...`

```bash
ingress:
  enabled: true
  annotations:
    cert-manager.io/issuer: "letsencrypt"
    traefik.ingress.kubernetes.io/router.middlewares: "default-large-upload@kubernetescrd"
  ingressClassName: traefik
  path: /
  hosts:
    - ${COMPANY_DOMAIN}
  tls:
  # this secret must exists or it can be created from a working cert-manager instance
    - secretName: mender-ingress-tls
      hosts:
        - ${COMPANY_DOMAIN}
global:
  s3:
    AWS_URI: "https://s3.ap-southeast-2.amazonaws.com"
    AWS_BUCKET: "${S3_BUCKET_NAME}"
    AWS_REGION: "ap-southeast-2"
    AWS_ACCESS_KEY_ID: ""
    AWS_SECRET_ACCESS_KEY: ""
    AWS_FORCE_PATH_STYLE: "false"
  url: "${MY_MENDER_WEBSITE_URL}"

api_gateway:
  storage_proxy:
    enabled: false
    url: "https://s3.ap-southeast-2.amazonaws.com"
    customRule: "PathRegexp(`^/konnext-mender`)"

```

---

<div class="post-metadata">

**Author:** ![robgio](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/robgio/32/1760_2.png) [@robgio](https://hub.mender.io/u/robgio)\
**Post date:** [July 4, 2025, 10:21am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/14 "2025-07-04T10:21:21Z")

</div>

@nicktech the thing is that it should work with the storage\_proxy enabled as well: it simply would route the requests from `https://${COMPANY_DOMAIN}/konnext-mender` to `"https://s3.ap-southeast-2.amazonaws.com"` as an origin. Which issues did you find with the storage proxy enabled?

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 10:44am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/15 "2025-07-04T10:44:25Z")

</div>

After setting up the mender server, I couldn’t download artifacts from the website. Then i found related posts on hub [Unable to Download Artifacts - Self-Hosted Mender Community Server 4.0.0 - #9 by antonio-mancuso-vado](https://hub.mender.io/t/unable-to-download-artifacts-self-hosted-mender-community-server-4-0-0/7663/9), and it resolved my issue. After disabling storage\_proxy, there weren’t any issues downloading artifacts.

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 4, 2025, 10:45am UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/16 "2025-07-04T10:45:16Z")

</div>

do you reckon this setting can potentially impact the connections between my server and client?

---

<div class="post-metadata">

**Author:** ![robgio](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/robgio/32/1760_2.png) [@robgio](https://hub.mender.io/u/robgio)\
**Post date:** [July 4, 2025, 12:03pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/17 "2025-07-04T12:03:41Z")

</div>

I’m not sure here.. I need to reproduce the S3 and the storage proxy issue.  
Anyway, this could have been a possible lead on your specific client issue, but now I can see no relation if you’re using plain S3. I’m not sure I could help you more than this on your case, sorry

---

<div class="post-metadata">

**Author:** ![lramirez](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/lramirez/32/1195_2.png) [@lramirez](https://hub.mender.io/u/lramirez)\
**Post date:** [July 4, 2025, 11:20pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/18 "2025-07-04T23:20:50Z")

</div>

Hello @nicktech, just making sure I understood the problem. Are you saying that after disabling storage\_proxy, now the client doesn’t error with:

```auto
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=23 severity=error time="2025-Jun-30 08:01:15.200322" name="Global" msg="Request to push status data failed: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "
Jun 30 08:01:15 konnexthome mender-update[810890]: record_id=24 severity=error time="2025-Jun-30 08:01:15.200493" name="Global" msg="Could not send deployment status: bad version: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "

```

I don’t see the relationship on downloading the artifact with the device not being able to report its status to the server. Or am I missing anything?

Assuming these are not related. I created internally a bug report [MEN-8554](https://northerntech.atlassian.net/browse/MEN-8554)

---

<div class="post-metadata">

**Author:** ![nicktech](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nicktech](https://hub.mender.io/u/nicktech)\
**Post date:** [July 5, 2025, 2:35pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/19 "2025-07-05T14:35:13Z")

</div>

> [@lramirez](#):
>
> ```auto
> 5 konnexthome mender-update[810890]: record_id=24 severity=error time="2025-Jun-30 08:01:15.200493" name="Global" msg="Could not send deployment status: bad version: PUT http://127.0.0.1:39193/api/devices/v1/deployments/device/deployments/d65af14a-681c-443f-9868-ceba3b4864cd/status: "
> 
> ```
> 
> I don’t see the relationship on downloa

Hi, it was two different problems. After disabling storage proxy, I could normally download artifaicts from the self-hosted mender website. The current problem is, my mender client could not properly interact with mender server due to the “bad version” HTTP error.

---

<div class="post-metadata">

**Author:** ![simonbuehler](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/simonbuehler/32/1828_2.png) [@simonbuehler](https://hub.mender.io/u/simonbuehler)\
**Post date:** [July 10, 2025, 5:44pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/20 "2025-07-10T17:44:44Z")

</div>

hey, i have the same issue, self hosted mender - i can download the url the clients wants to get manually ok - but i also get the error “bad version”

```js
Jul 10 17:39:33 qemux86-64 mender-update[326]: record_id=564 severity=warning time="2025-Jul-10 17:39:33.679402" name="http_resumer:client" msg="bad version: GET https://mender-server-459007-mender-storage-dev.storage.googleapis.com/<xxx>?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=<xxx>%2Feurope-west3%2Fs3%2Faws4_request&X-Amz-Date=20250710T173320Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3D%22captured_image_1742467876.jpg.mender%22&response-content-type=application%2Fvnd.mender-artifact&x-id=GetObject&X-Amz-Signature=0e738440d6b7842672f9971ab359ed1af379a24c8aaf1cef03c2f5d2603e485c: "

```

Any idea what’s causing this? I switched `storage_proxy`but no changes, and it works with browser download of the url

---

<div class="post-metadata">

**Author:** ![aashish](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@aashish](https://hub.mender.io/u/aashish)\
**Post date:** [July 14, 2025, 4:59pm UTC](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858/21 "2025-07-14T16:59:25Z")

</div>

exact same issue. I would appreciate any help on fixing this. The deployment keeps on failing due to this issue

```auto
2025-07-12 00:56:55.601 +0000 UTC info: Sending status update to server
2025-07-12 00:56:55.604 +0000 UTC error: Request to push status data failed: PUT http://127.0.0.1:40663/api/devices/v1/deployments/device/deployments/13764df3-554b-445b-a994-b58c4191daa0/status: 
2025-07-12 00:56:55.604 +0000 UTC error: Could not send deployment status: bad version: PUT http://127.0.0.1:40663/api/devices/v1/deployments/device/deployments/13764df3-554b-445b-a994-b58c4191daa0/status: 
2025-07-12 00:56:55.613 +0000 UTC info: Running State Script: /var/lib/mender/scripts/ArtifactInstall_Enter_00_fw-env-fix
2025-07-12 00:56:55.85 +0000 UTC info: Sending status update to server
2025-07-12 00:56:55.861 +0000 UTC error: Request to push status data failed: PUT http://127.0.0.1:40663/api/devices/v1/deployments/device/deployments/13764df3-554b-445b-a994-b58c4191daa0/status: 
2025-07-12 00:56:55.862 +0000 UTC error: Could not send deployment status: bad version: PUT http://127.0.0.1:40663/api/devices/v1/deployments/device/deployments/13764df3-554b-445b-a994-b58c4191daa0/status: 

```

[Next page](https://hub.mender.io/t/mender-client-failed-to-update-deployment-status/7858.md?page=2)