Felix Klein

EDIT: Turns out that the issue is due to my reverse proxy (haproxy). Direct connection works fine - seems this is probably related to the new CSRF code? The reason...

Hi, thanks for your reply @foosel. No im just using an standard haproxy setup as a transparent reverse proxy with a dedicated subdomain for octoprint and no sub path. It...

So I was able to investigate this a bit further - the issue is indeed in the CSRF validation. I was able to fix the issue by adding `http-request add-header...

Yeah, here's hoping this will get updated - really loved this tool :) Unfortunately, my Go skills are not quite good enough _yet_ for submitting a pull request..

Thanks for your swift reply! I just tried building and pushing without provenance, that seems to work, with plain docker at least - thanks! Pushing with Buildkit via earthly unfortunately...

I had a look at where the 401 is coming from, `container/container.go:126`; thats: ```go if ctx.Doer == nil || (setting.Service.RequireSignInView && ctx.Doer.IsGhost()) { apiUnauthorizedError(ctx) } ``` As a quick test,...

> Are those still have provenance on? I mean it's not unlikely that provenance is not supported yet by the Gitea Container Registry. Yes, i used `BUILDX_NO_DEFAULT_ATTESTATIONS=1` but could well...

> Ok I'm out, as I cannot reproduce the issue on my system, provenance push didn't fail for me. > > I have created an dind container with containerd image...

Allright, I got pushing in Actions to work. I was using ```yaml - name: login to container registry uses: docker/login-action@v2 with: registry: GITEA_HOST username: ${{ gitea.actor }} password: ${{ gitea.token...

@princemaple Yeah, i figured as much! Annoying that `gen_smtp` does not expose more information about this error.