[Bug]: Minio Service unable to login

[Flowko]

Description

after adding the minio service and setting up the configuration, it loads fine, but cant seem to be able to login

Minimal Reproduction (if possible, example repository)

• Add Minio service to your project
• Update domain and start the service

Error

no errors throwing on the logs, which is weird

Good to mention that i have it set up with cloudflare, not sure if thats what causing it to break

Version

v4.0.0-beta.285

[Flowko]

@andrasbacsai would love some help if you have some time, thank you

[nicnocquee]

I have the same issue too. My server runs in Hetzner.

[jozefbonnar]

I'm unable to produce your error? v4.0.0-beta.294

[Flowko]

i think it has to do with http/https issues we deal with, ill take a deep look into this, cuz it wont work with cloudflare if i set it up to be https, i have to change it to http and then let cloudflare handle the rest, but ill check, thanks

[nicnocquee]

Hey @Flowko I found the problem with set up here https://github.com/coollabsio/coolify/issues/2124#issuecomment-2161848837

[StianHaugland1]

I encountered this issue where I had set up my environment on a local network using a private DNS server that manages records for services like Minio and Coolify. The problem arose because I forgot to configure the Coolify host to use this DNS server (not through Coolify's UI but on the Ubuntu server itself). As a result, the Minio container couldn't resolve the internal URL, which led to an 'invalid login' error. Once I corrected the DNS server configuration on the host and rebooted, I was able to log in successfully🥳

[Flowko]

Thanks guys, i just had to reconfig my vps instance and cloudflare, reseted some stuff, now working as expected!

[jimmysafe]

@Flowko im having the exact same issue, how did you ended up configuring Cloudflare with Coolify to enable Minio login? im going insane and i cant figure out a way to serve Minio with https when using Cloudflare tunnels..

[Flowko]

@jimmysafe i honestly dont recall the steps, but before i was using Traefik, and it was configured with cloudflare throught their token and some config i added to work with subdomains, it was messy, but i moved to Caddy and it just works out of the box with it, all i had to do is keep the DNS records for the ip address, also my DNS validation is ON now and DNS server is set to: 1.1.1.1

here is my minio compose, i didnt change i think, but just for reference:

services:
  minio:
    image: 'quay.io/minio/minio:latest'
    command: 'server /data --console-address ":9001"'
    environment:
      - MINIO_SERVER_URL=$MINIO_SERVER_URL
      - MINIO_BROWSER_REDIRECT_URL=$MINIO_BROWSER_REDIRECT_URL
      - MINIO_ROOT_USER=$SERVICE_USER_MINIO
      - MINIO_ROOT_PASSWORD=$SERVICE_PASSWORD_MINIO
    volumes:
      - 'minio-data:/data'
    healthcheck:
      test:
        - CMD
        - curl
        - '-f'
        - 'http://127.0.0.1:9000/minio/health/live'
      interval: 5s
      timeout: 20s
      retries: 10

hope this helps

[jimmysafe]

Ok, thanks to a guy on Coolify Discord (amazing place with amazing people), i managed to fix the issue..

With CF tunnels don’t use the Minio one click deploy, instead spin up a new service with docker compose and paste this as docker-compose file:

services:
  minio:
    image: minio/minio
    environment:
      - 'MINIO_ROOT_USER=${SERVICE_USER_MINIO}'
      - 'MINIO_ROOT_PASSWORD=${SERVICE_PASSWORD_MINIO}'
    command: 'server --console-address ":9001" /data'
    healthcheck:
      test: 'sleep 5 && exit 0'
      interval: 2s
      timeout: 10s
      retries: 5
    volumes:
      - './volumes/storage:/data'

Also dont forget to append the port 9001 to the domain.

[MarioCakeDev]

I had the same issue. It didn't work for me either because the Minio UI and the API URL were behind another Traefik Reverse Proxy which send the requests to the http proxy endpoint. Changing the proxy to point to the https proxy port worked for me.

I have a setup like this: Client -> Bare Metal Server with OPNSense + Nginx reverse proxy -> Own Traefik Proxy -> Traefik Proxy by Coolify on Port 80 -> Service

On my own Traefik Proxy had to be changed to point to the https port: Client -> Bare Metal Server with OPNSense + Nginx reverse proxy -> Own Traefik Proxy -> Traefik Proxy by Coolify on Port 443 -> Service

(I don't want all the different proxies, but my system is currently build this way. Lot to do here ^^')

The domains for the Minio Urls shall have https set as a scheme. I had a infinite redirect loop from https to http and back if it was set to http.

[peaklabs-dev]

@MarioCakeDev Since using multiple reversed proxies is not supported and not recommended, and the other issues seem to be fixed, I will close this.