Hello everyone, i created several mender-production servers, but none of them have a working ‘release’ tab. this has probably to do with the minio and the mender-deployment container not been able to communicate & when i go to releases, i get an empty white screen [minio-mender] now the questi…

the problem was indeed as @drewmoseley suggested to do with the FQDN

Hi @genedupre , nothing immediately jumps out at me. We will definitely need the logs to help diagnose this. The following will pull all the logs into individual files: $ for i in $(./run ps | grep menderprod | cut -d_ -f2); do ./run logs $i > $i.log.txt; done I did see that you are using the sa…

hello @drewmoseley thank you for answering, i also think it will have to do with the FQDN, but maybe it is because i dont fully understand the documentation, in the production documentation , there is an example of s3. storage-proxy: networks: mender: aliase…

Yes, the alias under the storage-proxy setting the the URL that will be used for the Minio instance. Basically, the Mender server will store artifacts there and the URL generated when a deployment is created will be based off of that. That URL will be passed to the client for download of the new a…

FWIW, this is identical to the issue that I’m seeing at https://hub.mender.io/t/issue-with-mender-2-0-ui-blank-release-list-page/ I’d not thought to look at the storage yet, but I’ll do that now, please let me know if it makes a difference for you!

hello @drewmoseley thanks for informing me about that, i had the presumption that s3 was always meant using an amazon service. i edited the prod.yml to let the storage.proxy point to s3.mender.inuits.io and mender-deployments to DEPLOYMENTS_AWS_URI: https://s3.mender.inuits.io:9000 and rem…

so i was not finding the solution to the problem at all, so what ive done is make an exact copy of the Production installation | Mender documentation doc’s using the mender.example.com FQDN and by adding both (s3) mender.example.com in my /etc/hosts of my server & workstation using standard CERT…

Dd you add the - GATEWAY_IP=my.mender.server to your config under the mender-gui section? This is what solved it for me - everything was connecting fine with Minio apart from the UI container, and adding this in fixed the issue. Note that you can set - GATEWAY_IP to a hostname as well as an IP add…

Mender minio: trouble connecting with other containers

General Discussions

MBConsultingUK August 19, 2019, 3:34pm 6

Try the solution at Working with S3 instead of Minio - no artifacts found and blank releases page - it fixed my issue completely.

Topic		Replies	Views
Communication fail beteewn mender-deployments & minio General Discussions minio , deployment , s3	1	487	March 27, 2023
Issue: mender-deployments SerializationError General Discussions issue , mender-server , deployment , production , integration	29	2600	July 23, 2021
Working with S3 instead of Minio - no artifacts found and blank releases page General Discussions	10	3338	August 19, 2019
[Self-hosted Mender with Kubernetes] (OpenShift) Communication between mender-deployments and Minio General Discussions	13	2028	February 17, 2020
[Self-hosted Mender 1.7] Configuration to Use Amazon S3 General Discussions	8	2539	November 25, 2022

Mender minio: trouble connecting with other containers

Related topics