search

storj / gateway-st

Single-tenant, S3-compatible server to interact with the Storj network
Apache License 2.0
71 stars 19 forks source link

minio object browser doesn't work after recent minio update #52

Closed halkyon closed 2 years ago

halkyon commented 2 years ago

If you try accessing the endpoint where Gateway-ST is listening, you're presented with the login screen as usual, but attempts to login result in "Invalid UI version in the JSON-RPC response". Looking at the JSON, uiVersion is set to DEVELOPMENT.GOGET. Presumably, this needs to be a correct version for it to parse correctly.

This works correctly on Gateway-ST v1.5.1 that runs the old version of minio, but not with v1.6.0 running the new version.

Artur mentioned we should compile with the correct LD flags to get this working: https://github.com/storj/minio/blob/main/buildscripts/gen-ldflags.go

storjBuildBot commented 2 years ago

Change https://review.dev.storj.io/c/storj/gateway/+/6857 mentions this issue.

ghost commented 2 years ago

Hello again, thanks for your quick. This is also not the only issue I'm experiencing, I'm also getting signature mismatch if I try file list actions. The only thing that seems to work is list buckets, but not the files inside. I'm using a nginx reverse proxy in front of the gateway

amwolff commented 2 years ago

Hello again, thanks for your quick. This is also not the only issue I'm experiencing, I'm also getting signature mismatch if I try file list actions. The only thing that seems to work is list buckets, but not the files inside. I'm using a nginx reverse proxy in front of the gateway

It seems to me like the reverse proxy might be modifying headers or adding/stripping path/query part of the request's URL. The first thing I would do is check whether it's working without the reverse proxy correctly. If it works this way, try to examine what the proxy receives and whether it matches what's being sent by the client. If you need more help, please open a separate ticket for this. 🙂