Connect PD MinIO S3 to the API address your deployment actually serves. The browser Console and the API are different destinations, even when both use the same hostname.

Check host, port and TLS together

Review the account’s MinIO endpoint and Connect over SSL/TLS. A complete URL supplies its own scheme and port; when using host:port, keep the TLS choice consistent with that endpoint. Use the intended API port explicitly.

Ask the storage administrator to confirm that both S3 requests and MinIO administration requests reach the intended deployment through that API endpoint. A Console login page or browser redirect is not a successful API response. Console ports depend on deployment configuration; do not assume every server uses the same one.

Keep certificate and proxy checks specific

The billing server must trust the endpoint certificate and be able to resolve and reach its hostname. A private certificate requires the appropriate trust configuration or a trusted TLS endpoint; turning off certificate validation is not a repair.

Have the responsible administrator review proxy routing and signing-related hostname/path handling when requests work directly but fail through the proxy. Preserve the public API hostname used by applications and signed links. Rewriting a signed link to another hostname can invalidate it.

Verify both host and customer access

Run PD MinIO S3 → Settings → Test Connection and inspect the named administration or S3 failure for each account. It is a read-only check, not proof that every user or bucket write is allowed.

The customer tool must also reach its issued endpoint. An internal hostname reachable only by the billing server may pass the host test and still fail for customers. Use the customer connection guide to verify the actual issued address without exposing credentials.

See the PD MinIO S3 Blesta guide for related tasks, or explore the module.