# Self-hosted Mender 2.1 - Bug report: GATEWAY\_IP not set in default config

**URL:** https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959
**Category:** General Discussions
**Tags:** bug
**Created:** [August 23, 2019, 1:06pm UTC](https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959 "2019-08-23T13:06:19Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![will](https://avatars.discourse-cdn.com/v4/letter/w/90ced4/32.png) [@will](https://hub.mender.io/u/will)
#### Post date: [August 23, 2019, 1:06pm UTC](https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959/1 "2019-08-23T13:06:19Z")

</div>

I just followed the instructions at [https://docs.mender.io/2.1/administration/production-installation](https://docs.mender.io/2.1/administration/production-installation)  
and lost some time before finding that I had to set the undocumented `GATEWAY_IP`.

Symptoms:  
The RELEASES page fails to render with a lot of failed network requests to localhost.

Debugging:  
A bit of debugging shows that my `/ui/env.js` has an empty `rootUrl`:

```auto
mender_environment = {
    rootUrl: "",
   … snip ...
}

```

Going down the rabbit hole, in [entrypoint.sh](https://github.com/mendersoftware/gui/blob/master/entrypoint.sh) `ROOT_URL` depends on `GATEWAY_IP`  
And indeed `GATEWAY_IP` is missing from `mender-gui / environment` in [docker-compose.yml](https://github.com/mendersoftware/integration/blob/master/docker-compose.yml)

---

<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: [August 23, 2019, 1:12pm UTC](https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959/2 "2019-08-23T13:12:32Z")

</div>

Hi @will,

Thanks for reporting. We have had other reports of this on the forum, and it has been fixed in [master](https://github.com/mendersoftware/gui/pull/514) and the fix will be included in the 2.1 final release.

For reference here is the other thread,

> [@Working with S3 instead of Minio - no artifacts found and blank releases page](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946):
>
> Hey folks, Running Mender 2.1 via the docker-compose scripts for the production environment as documented, using LetsEncrypt certificates for the TLS connections. In order to see if I can fix the issues I’m encountering [here](https://hub.mender.io/t/mender-minio-trouble-connecting-with-other-containers/916/3) and [here](https://hub.mender.io/t/issue-with-mender-2-0-ui-blank-release-list-page/619) I thought I’d skip the storage completely and move over to S3. I followed the (very brief!) instructions at [https://docs.mender.io/2.1/administration/storage#s3-storage-backend](https://docs.mender.io/2.1/administration/storage#s3-storage-backend) and have created the appropriate YAML config, updated the run script to use that inst…