# Not finishing deployment
**URL:** https://hub.mender.io/t/not-finishing-deployment/6216
**Category:** General Discussions
**Created:** [September 25, 2023, 6:04am UTC](https://hub.mender.io/t/not-finishing-deployment/6216 "2023-09-25T06:04:24Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 25, 2023, 6:04am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/1 "2023-09-25T06:04:24Z")
Hello,
I have a problem about deployment, and I need your help. All services are up and running. There are no services that has problem when I type ./run ps. The problem that I am having right now is that the deployment of a basic txt.file is not finishing. I am sharing te screenshots of the UI and the log of the mender-deployment service here.
Note: I am using self hosted mender version 3.4.
Approximately, every 10 seconds (10000ms), the logs saying inprogress, pending and list are repeating in the network tag of the browser.
The output of the docker logs menderproduction\_mender-deployments\_1 is the following:
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 25, 2023, 8:43am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/2 "2023-09-25T08:43:28Z")
After a couple of tries, the deployment gave me the following failure log :
2023-09-25 08:10:29 +0000 UTC info: Running Mender client version: 3.5.1
2023-09-25 08:10:29 +0000 UTC warning: RetryPollIntervalSeconds is not defined
2023-09-25 08:10:29 +0000 UTC error: Error fetching scheduled update info: code (404)
2023-09-25 08:10:29 +0000 UTC error: Update fetch failed: error receiving scheduled update information server error message: 404 page not found
2023-09-25 08:10:29 +0000 UTC info: State transition: update-fetch [Download\_Enter] → fetch-install-retry-wait [Download\_Enter]
2023-09-25 08:10:29 +0000 UTC warning: UpdatePollIntervalSeconds is not defined
2023-09-25 08:40:29 +0000 UTC info: State transition: fetch-install-retry-wait [Download\_Enter] → update-fetch [Download\_Enter]
2023-09-25 08:40:30 +0000 UTC warning: RetryPollIntervalSeconds is not defined
2023-09-25 08:40:36 +0000 UTC error: Error fetching scheduled update info: code (404)
2023-09-25 08:40:36 +0000 UTC error: Update fetch failed: error receiving scheduled update information server error message: 404 page not found
2023-09-25 08:40:36 +0000 UTC info: State transition: update-fetch [Download\_Enter] → fetch-install-retry-wait [Download\_Enter]
2023-09-25 08:40:36 +0000 UTC warning: UpdatePollIntervalSeconds is not defined
2023-09-25 08:40:36 +0000 UTC info: State transition: fetch-install-retry-wait [Download\_Enter] → update-error [ArtifactFailure]
2023-09-25 08:40:36 +0000 UTC info: State transition: update-error [ArtifactFailure] → cleanup [Error]
2023-09-25 08:40:36 +0000 UTC info: State transition: cleanup [Error] → update-status-report [none]
Could you please help me ? Thanks in advance.
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 26, 2023, 8:27am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/3 "2023-09-26T08:27:01Z")
ANY HELP ? I also share the related section of the prod.yml file here:
I am not sure about DEPLOYMENTS\_AWS\_URI and DEPLOYMENTS\_AWS\_EXTERNAL\_URI. I set the external one same as my mender domain name, and set the DEPLOYMENTS\_AWS\_URI as minio:9000. I am trying to use minio not aws, so I am a little bit confused. I have only one domain by the way. Also, I am using version 3.4 with docker-compose option.
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 26, 2023, 9:12am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/4 "2023-09-26T09:12:12Z")
Hello @dekan ,
could you please verify if you could fetch the artifact storage? Preferably from the device itself, or from another host; you should issue something like this:
```auto
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export DEPLOYMENTS_AWS_EXTERNAL_URI=https://mymenderdomain.com
aws s3 ls --endpoint-url $DEPLOYMENTS_AWS_EXTERNAL_URI s3://mender-artifact-storage/
```
Specifically, the `DEPLOYMENTS_AWS_URI` is for internal communication only, and the `DEPLOYMENTS_AWS_EXTERNAL_URI` is the external storage URL, accessible from the devices.
The `AWS` names are confusing, but kept for history reasons; it’s safe to use Minio with them.
Another test could be downloading the Artifact from the UI.
Thanks
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 26, 2023, 10:20am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/5 "2023-09-26T10:20:31Z")
First of all, thank you so much for the reply.
I have tried to download the artifact(a basic txt file) from the UI, and it gave me 404 not found. What is the thing that I am doing wrong in this setup ?
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 26, 2023, 10:22am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/6 "2023-09-26T10:22:04Z")
Which URL is the UI providing to you?
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 26, 2023, 10:25am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/7 "2023-09-26T10:25:02Z")
[https://mymenderdomain.com/mender-artifact-storage/d4e75c24-0309-4708-96e3-8a7ab1c66af2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=mender-deployments%2F20230926%2Fus-east-1%2Fs3%2Faws4\_request&X-Amz-Date=20230926T101905Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3D"deneme.txt.mender"&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=f011c5521d9558a3a9a95681f6c376c4c69def7396f1c1713c197f7ee6f68528](https://mymenderdomain.com/mender-artifact-storage/d4e75c24-0309-4708-96e3-8a7ab1c66af2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=mender-deployments%2F20230926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230926T101905Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3D%22deneme.txt.mender%22&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=f011c5521d9558a3a9a95681f6c376c4c69def7396f1c1713c197f7ee6f68528)
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 26, 2023, 10:30am UTC](https://hub.mender.io/t/not-finishing-deployment/6216/8 "2023-09-26T10:30:03Z")
What about this test?
```auto
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export DEPLOYMENTS_AWS_EXTERNAL_URI=https://mymenderdomain.com
aws s3 ls --endpoint-url $DEPLOYMENTS_AWS_EXTERNAL_URI s3://mender-artifact-storage/
```
This should display the artifact S3 URI, if any…
Of course, you have to resolve [mymenderdomain.com](http://mymenderdomain.com) domain
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 26, 2023, 12:33pm UTC](https://hub.mender.io/t/not-finishing-deployment/6216/9 "2023-09-26T12:33:09Z")
I cannot execute the command starting with aws. I tried to install awscli, but I cannot do because of some errors that I cannot solve.
But, I have an idea that may causes this problem. Since I have changed the default port 443 to 44344, may the problem arises because of that? I am not including this port the DEPLOYMENTS\_AWS\_EXTERNAL\_URI.
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 26, 2023, 12:38pm UTC](https://hub.mender.io/t/not-finishing-deployment/6216/10 "2023-09-26T12:38:05Z")
Good point, the api-gateway (port 443 by default) is also a gateway for Minio. So you can either try falling it back to 443 or by setting DEPLOYMENTS\_AWS\_EXTERNAL\_URI=[https://mymenderdomain.com:44344](https://mymenderdomain.com:44344).
Also please set the protocol accordingly (http or https)
---
### Author:  [@dekan](https://hub.mender.io/u/dekan)
#### Post date: [September 26, 2023, 1:24pm UTC](https://hub.mender.io/t/not-finishing-deployment/6216/11 "2023-09-26T13:24:11Z")
Thank you so much, it works with no problem now.