You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MinIO redirects browser access requests to the configured server port (i.e. 127.0.0.1:9000) to the configured Console port. MinIO uses the hostname or IP address specified in the request when building the redirect URI. The URL and port must be accessible by the client for the redirection to work
This breaks the current development setup in 2 ways:
http://localhost:9000/ now redirects to http://localhost:<some_port>/ where <some_port> is dynamically generated at MinIO startup. Since this port isn't forwarded, you can't configure MinIO:
WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated.
Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD
API: http://10.10.0.2:9000 http://127.0.0.1:9000
Console: http://10.10.0.2:<some_port> http://127.0.0.1:<some_port>
Documentation: https://docs.min.io
WARNING: Console endpoint is listening on a dynamic port (<some_port>), please use --console-address ":PORT" to choose a static port.
Even if you manually add the --console-address setting and forward the appropriate port, the instructions in step 7 still don't make sense, since there doesn't seem to be a static bucket anywhere and the UI is different.
The text was updated successfully, but these errors were encountered:
Latest MinIO version requires some changes to use `--console-address`. Also, the
new version of MinIO will require to update the documentation from our
installation guide.
Let's pin it for now to fix the immediate issue and come back with the proper solution.
Solution taken from @astrojuanlu's comment readthedocs/readthedocs.org#8332 (comment)
Details
4 days ago, a new version of MinIO was released. It contains the following breaking change:
This breaks the current development setup in 2 ways:
http://localhost:9000/
now redirects tohttp://localhost:<some_port>/
where<some_port>
is dynamically generated at MinIO startup. Since this port isn't forwarded, you can't configure MinIO:Even if you manually add the
--console-address
setting and forward the appropriate port, the instructions in step 7 still don't make sense, since there doesn't seem to be astatic
bucket anywhere and the UI is different.The text was updated successfully, but these errors were encountered: