@girish I've tried various approaches based on using minio-api.domain.tld
and the standard 443
port :
- Forklift
- MountainDuck
- Transmit
- S3FS
None of them connect properly.
I haven't tried Expandrive but don't expect any different.
Even the "official" Minio mc
CLI app (https://docs.min.io/docs/minio-client-complete-guide.html) fails with this message.
$ mc ls minio
mc: <ERROR> Unable to list folder. Get "https://minio-api.domain.tld/": x509: certificate
is not valid for any names, but wanted to match minio-api.domain.tld
I'm no expert but I'm starting to think there is an issue with Cloudron's minio implementation. Maybe simply that the certificate for the installed app is valid for the console url, e.g. minio.domain.tld but not for minio-api.domain.tld
I'm not sure how to properly test the certificate for minio-api.domain.tld, but a clumsy attempt to visit https://minio-api.domain.tld
(without expecting it to render a page) gives the standard certificate problem response :
Your connection is not private
Attackers might be trying to steal your information from minio-api.domain.tld (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
This server could not prove that it is minio-api.domain.tld; its security certificate does not specify Subject Alternative Names. This may be caused by a misconfiguration or an attacker intercepting your connection.
Is it dumb to question whether minio-api.domain.tld
can actually be verified by connecting apps ?
Why else would Minio's mc
app fail to connect ?