Questions[minio](server)

Greetings from Mehedy Hasan. I am using minio from the last 1 year. Recently I am facing infrastructure-related issues. The infrastructure setup configuration is as follows as-

OS: Ubuntu 20 Processor: 4 core RAM: 16 GB Network Speed: 1Gbps Storage: SSD

When an outgoing open port is over 1000, then the user-facing buffering and server connection timeout issues. I have a monitoring system where found CPU is use >20% and RAM use 8GB only also network speed is use 500Mbps.

After may short analysis I found that this problem is OS level. Maybe a high-performance configuration issue or port limitations.

Please help me as soon as possible if you get any issues.

I've installed minio on a VPS (running Ubuntu 20) with SSL via CERTBOT. When I connect to this site from my laptop, everything works fine, the certificate is valid. If I try to connect to this site from my windows server 20019 from which I want to connect to the storage location, I get an error that the certificate is not valid. When I check who has issued the certificate it says credo02-fw01.belbone.local. When I check it from my laptop it says R3.

I cannot find what could be the problem that it gives another issuer.

Any help/suggestions?

Kind Regards

We use MinIO as our storage server. The issue is that the objects are accessible to the public Internet. To solve this issue someone suggested to use crossdomain.xml file to restrict access to resources if the request is initiated from our domain only. However from what I read everywhere, it looks like that file is exclusive to Adobe products.

Is that correct? And if yes, what is the alternative solution?

Our webserver is nginx.

My MinIO API is listening on IP of the server and port 9000. It works fine.

However, if I try to change the port to 80 and restart the service, it fails to start:

● minio.service - MinIO
     Loaded: loaded (/etc/systemd/system/minio.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2021-10-25 12:37:04 CEST; 1s ago
       Docs: https://docs.min.io
    Process: 27026 ExecStartPre=/bin/bash -c if [ -z "${MINIO_VOLUMES}" ]; then echo "Variable MINIO_VOLUMES not set in>
    Process: 27027 ExecStart=/usr/local/bin/minio server $MINIO_OPTS $MINIO_VOLUMES (code=exited, status=1/FAILURE)
   Main PID: 27027 (code=exited, status=1/FAILURE)

Oct 25 12:37:03 hel-sto-01 systemd[1]: minio.service: Main process exited, code=exited, status=1/FAILURE
Oct 25 12:37:03 hel-sto-01 systemd[1]: minio.service: Failed with result 'exit-code'.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Scheduled restart job, restart counter is at 5.
Oct 25 12:37:04 hel-sto-01 systemd[1]: Stopped MinIO.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Start request repeated too quickly.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Failed with result 'exit-code'.
Oct 25 12:37:04 hel-sto-01 systemd[1]: Failed to start MinIO.

It's a fresh Ubuntu 20.04 server and I have nothing listening on port 80.

As soon as I revert back to port 9000, MinIO works normally.

Please assist.

I'm trying to use the MinIO operator on a minikube (1 node) deployed in an EC2 machine. The operator is deployed correctly and the same is for the tenant creation and it seems all good until I try to make a connection to the created tenant. In this case I receive a 500 internal server error then I'm unable to create buckets or to use the mc client that MinIO provides. I tried both with the MinIO console (using a port-forward) and the command line minio command to create the tenant and both worked.

This is what I see with kubectl:

mc test: https://isstatic.aoverflow.com/qFmKj.png

kubectl get all -n minio-tenant-aisync: https://isstatic.aoverflow.com/zPJCk.png

kubectl get all --all-namespaces: https://isstatic.aoverflow.com/g8R8t.png

I am new to Kubernetes and MinIO then I don't know if I am missing something, could you help me please?