🙋🏻 Traefik 2.11 breaks Dozzle (fixed) about dozzle HOT 15 CLOSED

This is Traefik related. Had the same issue. Downgraded Traefik from latest (2.11.1) to 2.10.7 and it works like a charm. It didn't affect just Dozzle but my other containers too.

from dozzle.

Closing since it looks like it is fixed.

from dozzle.

@FrancYescO I use Traefik myself in production. I haven't seen this. If you can figure which version broke it then I can do a diff. Did anything change on your side?

from dozzle.

From the gif it looks like the event stream is failing. Does Dozzle show any errors in logs?

from dozzle.

Ah yes, I have been running 2.10. Looks like I will hold updating 🤣

from dozzle.

2.11.2 is available now. Didn't try it yet :)

from dozzle.

jesus.. @blaze6x6 thanks moving traefik back to tag v2.10 solved

seems it totally breaks up HTTPs stream randomly dropping the TCP stream (dozzle is just one of the service that it was breaking)

from dozzle.

2.11.2 is available now. Didn't try it yet :)

seems not.. :latest :v2.11 :3.0 tags of traefik have this issue and random 499 Client Closed Request errors

from dozzle.

Looking at the changelog, looks like a lot was changed regarding timeout for live connections.

A lot of clients are going to be broken if their connection keeps getting closed.

from dozzle.

btw, just to better manage this cases on dozzle side.. i think you can avoid "resetting" the full ui and just keep the last received content like cached

from dozzle.

There is some historical reasons. Caching of the container list is complicated because containers can also be deleted and the UI wouldn't know. I could do a diff but for now kept it simple.

The logs is more complicated. I found in some edge cases the browser disconnecting would cause a memory leak and the only solution was to just delete the buffer.

from dozzle.

I just had this issue with Traefik 2.11.2

I downgraded to 2.10.1 and everything works properly for me now.

from dozzle.

Are you sure you were on 2.11.2? I am on latest version for about 20 hours now with no issues on any of my container.

from dozzle.

Hmm .. maybe the one before that, but I just downgraded to 2.10 and that fixed everything for me.

from dozzle.

maybe i was having the v2.11 tag cached to 2.11.1 .. actually pulling :latest (2.11.2) is working

from dozzle.