# Working with S3 instead of Minio - no artifacts found and blank releases page

**URL:** <https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946>\
**Category:** General Discussions\
**Created:** [August 19, 2019, 6:27am UTC](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946 "2019-08-19T06:27:28Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![peter](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@peter](https://hub.mender.io/u/peter)\
**Post date:** [August 19, 2019, 2:23pm UTC](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946/9 "2019-08-19T14:23:54Z")

</div>

as a workaround you could add to gui section in `docker-compose.yml` (in the top level directory) environment variable `GATEWAY_IP=yourdomain`

so it looks something like this:

```auto
    mender-gui:
        image: mendersoftware/gui:2.1.0b1
        extends:
            file: common.yml
            service: mender-base
        networks:
            - mender
        environment:
            - INTEGRATION_VERSION
            - MENDER_ARTIFACT_VERSION
            - MENDER_VERSION
            - MENDER_DEB_PACKAGE_VERSION
            - GATEWAY_IP=my.mender.server

```

peter

---

_[View the full topic](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946)._