# Can not fetch update image on deployent **URL:** \ **Category:** General Discussions\ **Created:** [December 1, 2023, 10:31am UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394 "2023-12-01T10:31:34Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Trankil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/trankil/32/2065_2.png) [@Trankil](https://hub.mender.io/u/Trankil)\ **Post date:** [December 1, 2023, 10:31am UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/1 "2023-12-01T10:31:34Z")
Hi, I recently install mender 3.4 with Docker compose. The server was working, I have already launched deployments on devices. We received a new device from a supplier, I configured the Mender client and tried to update it. The deployment failed with the following logs: ```auto 2023-11-27 09:30:08 +0000 UTC info: Running Mender client version: 2.6.0-dirty 2023-11-27 09:30:08 +0000 UTC error: Can not fetch update image: Get "https:///mender-artifact-storage/62ff65b5-6cb8-49b4-9fee-c46ec57cc4dc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=mender-deployments%2F20231127%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231127T093008Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=d5f7eeed59f27dfc06052a697afde00e0d59e2d0487f94e6e579489242c4cdb7": http: no Host in request URL 2023-11-27 09:30:08 +0000 UTC error: Update fetch failed: update fetch request failed: Get "https:///mender-artifact-storage/62ff65b5-6cb8-49b4-9fee-c46ec57cc4dc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=mender-deployments%2F20231127%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231127T093008Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=d5f7eeed59f27dfc06052a697afde00e0d59e2d0487f94e6e579489242c4cdb7": http: no Host in request URL 2023-11-27 09:30:08 +0000 UTC info: State transition: update-fetch [Download_Enter] -> fetch-install-retry-wait [Download_Enter] 2023-11-27 09:31:08 +0000 UTC info: State transition: fetch-install-retry-wait [Download_Enter] -> update-fetch [Download_Enter] ``` The supplier manages to update remotely without encountering this problem. I don’t understand where this problem comes from. Did anyone have an idea? Thank you in advance for your answers ---
**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:** [December 1, 2023, 12:26pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/2 "2023-12-01T12:26:28Z")
@Trankil nothing that immediately strikes me. Client version 2.6…0-dirty sounds a bit suspicious, it indicates an old and possibly patched up thing. Does this also happen on the current maintained version? Plus, does manually pulling the artifact work? @robgio maybe can share some thoughts too. Greetz, Josef ---
**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:** [December 1, 2023, 1:08pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/3 "2023-12-01T13:08:12Z")
@Trankil could it be a network problem in the new device? `http: no Host in request URL` Can you try to run some troubleshooting command from the device? E.g.: ```auto dig mender-artifact-storage ping mender-artifact-storage curl https:///mender-artifact-storage/62ff65b5-6cb8-49b4-9fee-c46ec57cc4dc?X-Amz-Algorithm=. ``` ---
**Author:** ![Trankil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/trankil/32/2065_2.png) [@Trankil](https://hub.mender.io/u/Trankil)\ **Post date:** [December 1, 2023, 2:33pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/4 "2023-12-01T14:33:10Z")
The supplier provided us with the equipment with this version, we are not supposed to modify it… What do you mean by manually pulling the artifact ? ---
**Author:** ![Trankil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/trankil/32/2065_2.png) [@Trankil](https://hub.mender.io/u/Trankil)\ **Post date:** [December 1, 2023, 2:36pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/5 "2023-12-01T14:36:43Z")
dig: command not found curl: (6) Could not resolve host: mender-artifact-storage ping: mender-artifact-storage: Name or service not known mender-artifact-storage is not a local address for docker compose? ---
**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:** [December 1, 2023, 2:39pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/6 "2023-12-01T14:39:05Z")
@Trankil see the post by @robgio, the `curl` invocation does manually download (slang: “pull”) the artifact from the server. Please understand that especially concerning outdated packages and self-hosted instances of the open source backend our support options are very limited. Concerning your answer to @robgio: if you cannot `ping` a name, then name resolution does not work. Hence, no tool will be able to download anything from it. So something with the network configuration is wrong in this case. Greetz, Josef ---
**Author:** ![Trankil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/trankil/32/2065_2.png) [@Trankil](https://hub.mender.io/u/Trankil)\ **Post date:** [December 1, 2023, 2:47pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/7 "2023-12-01T14:47:27Z")
> [@TheYoctoJester](#): > > Joseph I don’t understand what the domain name “mender-artifact-storage” means because it is not that of my server. What does this domain name correspond to? Where can I modify it? ---
**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:** [December 1, 2023, 2:50pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/8 "2023-12-01T14:50:10Z")
Look at `/etc/mender.conf`, as documented [here](https://docs.mender.io/client-installation/configuration-file). This is probably set by your supplier. I strongly suggest you contact them to get it sorted out. Greetz, Josef ---
**Author:** ![levantung](https://avatars.discourse-cdn.com/v4/letter/l/919ad9/32.png) [@levantung](https://hub.mender.io/u/levantung)\ **Post date:** [March 19, 2025, 3:44am UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/9 "2025-03-19T03:44:07Z")
hi @Trankil i have issue the same , how did you fix this error ![image](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/2/27822876b888c70d39ccf7f226d48442528c2da9.jpeg) ![image](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/c/cf70a986b018cc8505498baa603fa46bcd2a900e.png) ---
**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:** [March 20, 2025, 12:06pm UTC](https://hub.mender.io/t/can-not-fetch-update-image-on-deployent/6394/10 "2025-03-20T12:06:35Z")
@levantung make sure that `s3.docker.mender.io` also resolves to 10.2.5.218, usually by adding the entry to your `/etc/hosts` file. Greetz, Josef