HTTP 403 after fresh deployment

General Discussions
1

Hello,

I have just deployed a new cluster and wanted to install Mender. However, after following the guide (Production installation with Kubernetes | Mender documentation), all the pods are healthy, but I’m getting a 403 as a response…? I can’t see the login screen or anything :frowning:
Inspecting the API logs, I can see:

{"ClientAddr":"10.244.226.207:50588","ClientHost":"10.244.226.207","ClientPort":"50588","ClientUsername":"-","DownstreamContentSize":223,"DownstreamStatus":403,"Duration":435679,"OriginContentSize":223,"OriginDuration":378469,"OriginStatus":403,"Overhead":57210,"RequestAddr":"mender.staging.avelon.biz","RequestContentSize":0,"RequestCount":874,"RequestHost":"mender.staging.avelon.biz","RequestMethod":"GET","RequestPath":"/favicon.ico","RequestPort":"-","RequestProtocol":"HTTP/1.1","RequestScheme":"http","RetryAttempts":0,"RouterName":"storage_proxy@file","ServiceAddr":"seaweedfs-s3:8333","ServiceName":"storage_proxy@file","ServiceURL":"http://seaweedfs-s3:8333","SpanId":"0000000000000000","StartLocal":"2025-04-02T11:58:15.650590442Z","StartUTC":"2025-04-02T11:58:15.650590442Z","TraceId":"00000000000000000000000000000000","entryPointName":"http","level":"info","msg":"","time":"2025-04-02T11:58:15Z"}

Any ideas?

Thank you!

2

Hello @silviub , it looks like you’re hitting the storage provider (Seaweedfs) instead of the Mender Server UI. Could you please share your Ingress information and your values file (of course without any secret)?

Thanks

3

Hey,

Thanks for the answer. I wasn’t hitting Seaweedfs, since the logs above were observed in the API pod. Still, it seems that I have somehow managed to have the wrong SECRET_KEY_ID and SECRET_ACCESS_KEY values, and that’s why it was returning 403.
As an improvement, maybe show a message, somethink like “Cannot connect to Storage” would be helpful, I think :slight_smile:

Thank you.