# Demo Server 2.3.0

**URL:** https://hub.mender.io/t/demo-server-2-3-0/1645
**Category:** General Discussions
**Created:** [March 13, 2020, 3:54pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645 "2020-03-13T15:54:06Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![spinarr](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/spinarr/32/527_2.png) [@spinarr](https://hub.mender.io/u/spinarr)
#### Post date: [March 13, 2020, 3:54pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/1 "2020-03-13T15:54:06Z")

</div>

Hello, having trouble to run demo server:

Creating integration230\_mender-gui\_1\_4b9335dd528b … done  
Creating integration230\_mender-elasticsearch\_1\_4309b5c40743 … done  
Creating integration230\_minio\_1\_7d97eeac20bc … done  
Creating integration230\_mender-redis\_1\_7e26e6d0aebb … done  
Creating integration230\_mender-mongo\_1\_30cda881b9b1 … done  
Creating integration230\_mender-useradm\_1\_56daa776cb7e … done  
Creating integration230\_mender-create-artifact-worker\_1\_ec4c17a15843 … done  
Creating integration230\_mender-workflows-server\_1\_8e477cfb4f1a … done  
Creating integration230\_mender-inventory\_1\_63fcfeab5bc4 … done  
Creating integration230\_mender-conductor\_1\_a47a07641787 … done  
Creating integration230\_mender-device-auth\_1\_3ec7fb897048 … done  
Creating integration230\_storage-proxy\_1\_f8d61b584c53 … done  
Creating integration230\_mender-deployments\_1\_6e7c6cf8454c … done  
Creating integration230\_mender-api-gateway\_1\_4aba646fbdba … done  
Creating a new user…  
Error: No such container: integration230\_mender-useradm\_1  
docker exec error: 1

f971a3694dda mendersoftware/api-gateway:2.1.0 “/entrypoint.sh” 4 minutes ago Up 4 minutes 80/tcp, 0.0.0.0:443-\>443/tcp integration230\_mender-api-gateway\_1\_baff9a06a615  
acd3eb71c615 mendersoftware/deployments:1.9.0 “/entrypoint.sh --coâŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-deployments\_1\_ebdde34e7ee8  
440dd4d88601 openresty/openresty:1.13.6.2-0-alpine “/usr/local/openrestâŚ” 4 minutes ago Up 4 minutes 0.0.0.0:9000-\>9000/tcp integration230\_storage-proxy\_1\_cab9f64c837e  
32605c26bbe1 mendersoftware/deviceauth:2.2.0 “/usr/bin/deviceauthâŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-device-auth\_1\_6555c7a6038e  
8e46a3afcf0e mendersoftware/mender-conductor:1.6.0 “/srv/start\_conductoâŚ” 4 minutes ago Up 4 minutes (healthy) 0.0.0.0:8080-\>8080/tcp, 8090/tcp integration230\_mender-conductor\_1\_960390ad2873  
ceb7cfb4323d mendersoftware/inventory:1.7.0 “/usr/bin/inventory âŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-inventory\_1\_92e4c7f3e31a  
2fc30f024d75 mendersoftware/useradm:1.10.0 “/usr/bin/useradm --âŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-useradm\_1\_577b9e087812  
6e66404cca8a mendersoftware/workflows:1.0.0 “/usr/bin/workflows âŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-workflows-server\_1\_aa43d1b0d666  
23cee4b21d09 mendersoftware/create-artifact-worker:1.0.0 “/usr/bin/workflows âŚ” 4 minutes ago Up 4 minutes 8080/tcp integration230\_mender-create-artifact-worker\_1\_6f2017edf96c  
81a264a02f05 mongo:3.6 “docker-entrypoint.sâŚ” 4 minutes ago Up 4 minutes 27017/tcp integration230\_mender-mongo\_1\_353324f2329f  
53ac27732497 redis:5-alpine3.8 “/redis/entrypoint.sh” 4 minutes ago Up 4 minutes 6379/tcp integration230\_mender-redis\_1\_147824f4647a  
138ae158b453 minio/minio:RELEASE.2018-09-25T21-34-43Z “/usr/bin/docker-entâŚ” 4 minutes ago Up 4 minutes (healthy) 9000/tcp integration230\_minio\_1\_889f39169949  
962129dea08e elasticsearch:6.8.6 “/usr/local/bin/dockâŚ” 4 minutes ago Up 4 minutes 9200/tcp, 9300/tcp integration230\_mender-elasticsearch\_1\_bfa24d385c1f  
ec4f6ab1a08a mendersoftware/gui:2.3.0 “/entrypoint.sh nginx” 4 minutes ago Up 4 minutes 80/tcp integration230\_mender-gui\_1\_9f7adfdb4e9a

docker logs integration230\_mender-useradm\_1\_577b9e087812  
time=“2020-03-13T15:43:15Z” level=info msg=“User Administration Service, version unknown starting up” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“running migrations in single tenant mode” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“automigrate is ON, will apply migrations” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“migrating useradm” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“applying migration from version 0.0.0 to 0.1.0” db=useradm file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“setting up prod middleware” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:15Z” level=info msg=“listening on :8080” file=entry.go func=“logrus.(\*Entry).Logf” line=313  
time=“2020-03-13T15:43:45Z” level=warning msg=“Failed to extract identity from header: unknown authorization method Basic” file=entry.go func=“logrus.(\*Entry).Logf” line=313 request\_id=27d490f4-06e3-4b10-97a6-56320df4139e  
time=“2020-03-13T15:43:45Z” level=error msg=unauthorized file=entry.go func=“logrus.(\*Entry).Error” line=296 request\_id=27d490f4-06e3-4b10-97a6-56320df4139e  
time=“2020-03-13T15:43:45Z” level=info msg=“401 768Îźs POST /api/management/v1/useradm/auth/login HTTP/1.0 - curl/7.58.0” file=entry.go func=“logrus.(\*Entry).Info” line=284 request\_id=27d490f4-06e3-4b10-97a6-56320df4139e

Many thanks for guidance.  
Rostislav

---

<div class="post-metadata">

### Author: ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)
#### Post date: [March 13, 2020, 7:22pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/2 "2020-03-13T19:22:27Z")

</div>

@spinarr Hello, can you please tell me the version number of your docker-compose?

`$ docker-compose --version`

I suspect you are using docker-compose version 1.23.0 or 1.23.1, which appends hashes to containers name. This behaviour has been reverted in 1.23.2. If this is the case, can you please upgrade (or downgrade) your docker-compose and try again?

---

<div class="post-metadata">

### Author: ![spinarr](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/spinarr/32/527_2.png) [@spinarr](https://hub.mender.io/u/spinarr)
#### Post date: [March 13, 2020, 9:17pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/3 "2020-03-13T21:17:43Z")

</div>

Yes. Many thanks.

---

<div class="post-metadata">

### Author: ![spinarr](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/spinarr/32/527_2.png) [@spinarr](https://hub.mender.io/u/spinarr)
#### Post date: [March 23, 2020, 9:55am UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/4 "2020-03-23T09:55:42Z")

</div>

Hello,

in order to connect the device to our running demo server do we need to distribute certificates to the device client?

Many thanks  
Rostislav

---

<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: [March 23, 2020, 12:45pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/5 "2020-03-23T12:45:44Z")

</div>

For the demo server we do have a set of certificates that you need to use, it can be found [here](https://github.com/mendersoftware/mender/blob/master/support/demo.crt).

It depends a bit on how you are installing the Mender client, as these might already be installed on your device.

---

<div class="post-metadata">

### Author: ![spinarr](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/spinarr/32/527_2.png) [@spinarr](https://hub.mender.io/u/spinarr)
#### Post date: [March 23, 2020, 12:58pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/6 "2020-03-23T12:58:33Z")

</div>

Great, one of our device is in demo server.

Is there a way to name devices in the image so that when they appear in dashboard we have a way to distinguish them?

Thanks.  
Rostislav

---

<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: [March 23, 2020, 1:20pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/7 "2020-03-23T13:20:18Z")

</div>

You would typically customize the [Device identity](https://docs.mender.io/2.3/client-configuration/identity) to achieve this. Let me know if it needs additional clarifications.

---

<div class="post-metadata">

### Author: ![spinarr](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/spinarr/32/527_2.png) [@spinarr](https://hub.mender.io/u/spinarr)
#### Post date: [April 16, 2020, 12:21pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/8 "2020-04-16T12:21:02Z")

</div>

Hi,

we are doing first update with our demo server and facing fail.  
GW device is connected to our server.

Any pointers are much appreciated.

```auto
2020-04-15 23:40:52 +0000 UTC info: Running Mender version 2.2.0
2020-04-15 23:40:52 +0000 UTC debug: handle update fetch state
2020-04-15 23:40:53 +0000 UTC debug: status reported, response 204 No Content
2020-04-15 23:40:53 +0000 UTC error: Can not fetch update image: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T234052Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=0d1d75eeac51335d1fc08def0be8b3882729e86fdad255e1f6a0bb1fd6eee081: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host
2020-04-15 23:40:53 +0000 UTC error: update fetch failed: update fetch request failed: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T234052Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=0d1d75eeac51335d1fc08def0be8b3882729e86fdad255e1f6a0bb1fd6eee081: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host
2020-04-15 23:40:53 +0000 UTC info: State transition: update-fetch [Download_Enter] -> fetch-install-retry-wait [Download_Enter]
2020-04-15 23:40:53 +0000 UTC debug: handle fetch install retry state
2020-04-15 23:40:53 +0000 UTC debug: wait 30m0s before next fetch/install attempt
2020-04-15 23:58:10 +0000 UTC info: Running Mender version 2.2.0
2020-04-15 23:58:10 +0000 UTC error: Update was interrupted in state: update-fetch
2020-04-15 23:58:10 +0000 UTC info: Update Module path "/usr/share/mender/modules/v3" could not be opened (open /usr/share/mender/modules/v3: no such file or directory). Update modules will not be available
2020-04-15 23:58:10 +0000 UTC info: State transition: init [none] -> idle [Idle]
2020-04-15 23:58:10 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2020-04-15 23:58:11 +0000 UTC info: Running Mender version 2.2.0
2020-04-15 23:58:11 +0000 UTC debug: handle update fetch state
2020-04-15 23:58:11 +0000 UTC debug: status reported, response 204 No Content
2020-04-15 23:58:11 +0000 UTC error: Can not fetch update image: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T235811Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=b519d7518d8923f02c850b98016038e3c39eec8898e04135b8e82a3d5723eb8c: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host
2020-04-15 23:58:11 +0000 UTC error: update fetch failed: update fetch request failed: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T235811Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=b519d7518d8923f02c850b98016038e3c39eec8898e04135b8e82a3d5723eb8c: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host
2020-04-15 23:58:11 +0000 UTC info: State transition: update-fetch [Download_Enter] -> fetch-install-retry-wait [Download_Enter]
2020-04-15 23:58:11 +0000 UTC debug: handle fetch install retry state
2020-04-15 23:58:11 +0000 UTC debug: wait 1m0s before next fetch/install attempt
2020-04-15 23:59:11 +0000 UTC debug: wait complete
2020-04-15 23:59:11 +0000 UTC info: State transition: fetch-install-retry-wait [Download_Enter] -> update-fetch [Download_Enter]
2020-04-15 23:59:11 +0000 UTC debug: handle update fetch state
2020-04-15 23:59:11 +0000 UTC debug: status reported, response 204 No Content
2020-04-15 23:59:11 +0000 UTC error: Can not fetch update image: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T235811Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=b519d7518d8923f02c850b98016038e3c39eec8898e04135b8e82a3d5723eb8c: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host
2020-04-15 23:59:11 +0000 UTC error: update fetch failed: update fetch request failed: Get https://s3.docker.mender.io:9000/mender-artifact-storage/6f52b4d2-3335-4210-9629-e25e3967ba37?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=minio%2F20200415%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200415T235811Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=b519d7518d8923f02c850b98016038e3c39eec8898e04135b8e82a3d5723eb8c: dial tcp: lookup s3.docker.mender.io on 10.0.1.138:53: no such host

```

Is there any reason to connect to [mender.io](http://mender.io)?

```auto
root@orange-pi-zero:~# cat /etc/mender/mender.conf
{
    "InventoryPollIntervalSeconds": 28800,
    "RetryPollIntervalSeconds": 300,
    "ServerURL": "https://mender.iqrf.org",
    "TenantToken": "dummy",
    "UpdatePollIntervalSeconds": 1800
}root@orange-pi-zero:~#

```

---

<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: [April 16, 2020, 12:37pm UTC](https://hub.mender.io/t/demo-server-2-3-0/1645/9 "2020-04-16T12:37:59Z")

</div>

> [@spinarr](#):
>
> [s3.docker.mender.io](http://s3.docker.mender.io) on 10.0.1.138:53

In the demo example we use `s3.docker.mender.io` and `docker.mender.io` as domains for which we also provide a demo certificate for which is required by https.

To have the domains resolve correctly, you must add an entry in `/etc/hosts` on the device, e.g

```auto
192.168.1.100 s3.docker.mender.io docker.mender.io

```

Replace `192.168.1.100` above with the actual IP address of the PC running the demo server
