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
I spun up filestash within my local k8s cluster to be able to browser my minio instance within this. After specifying the service dns name and port, I get an "Invalid account" when trying to connect. After turning on debug logging, I noticed the following in the logs.
2024/10/28 22:03:14 SYST DEBUG session::auth 'GetHome' RequestError: send request failed
caused by: Get "https://minio.minio.svc.cluster.local:3900/": http: server gave HTTP response to HTTPS client
Step by step instructions to reproduce the bug
Setup local s3 through something like minio. Point filestash at the HTTP port instead of a HTTPS port.
Can you replicate that error from the demo?
No I can't because I ran into this issue with a local service. Might be possible if there's as S3 API exposed over HTTP somewhere.
Observed behavior
Unable to connect using S3 over plain HTTP.
Expected behavior
I would have expected there to be some obvious way to toggle it to use plain HTTP.
The text was updated successfully, but these errors were encountered:
Description of the bug
I spun up filestash within my local k8s cluster to be able to browser my minio instance within this. After specifying the service dns name and port, I get an "Invalid account" when trying to connect. After turning on debug logging, I noticed the following in the logs.
2024/10/28 22:03:14 SYST DEBUG session::auth 'GetHome' RequestError: send request failed
caused by: Get "https://minio.minio.svc.cluster.local:3900/": http: server gave HTTP response to HTTPS client
Step by step instructions to reproduce the bug
Setup local s3 through something like minio. Point filestash at the HTTP port instead of a HTTPS port.
Can you replicate that error from the demo?
No I can't because I ran into this issue with a local service. Might be possible if there's as S3 API exposed over HTTP somewhere.
Observed behavior
Unable to connect using S3 over plain HTTP.
Expected behavior
I would have expected there to be some obvious way to toggle it to use plain HTTP.
The text was updated successfully, but these errors were encountered: