This message was deleted.

Hi @freezing-holiday-13112, could you export an higher

TRACE_LEVEL

env var to get some logs? In your shell for the cli, and in the epinio deployment for the server

So in the console for my epinio cli I just place TRACE_LEVEL without a value?

Sorry, I forgot to add the value. It should be an integer, something like

20

will work fine

So to do that I do a helm update with epinio?

I don't think it's doable with Helm, I usually use this one-shot command with kubectl:

TRACE_LEVEL=20 && kubectl patch deployment -n epinio epinio-server --patch '{"spec": {"template": {"spec": {"containers": [{"name": "epinio-server","env": [{"name":"TRACE_LEVEL", "value":"'"$TRACE_LEVEL"'"}]}]}}}}'

When I look at the logs they look good to me

hi @freezing-holiday-13112, sorry for the late reply. Since that there seems to be no errors on the Epinio side maybe is something that is happening on another layer, in the ingress probably. Which is your setup (kubernetes version/type, epinio version, and everything)?