I recently upgraded my k3s traefik deployment from 3.6.13 to 3.6.15, and discovered the the fail2ban plugin was silently failing; its failure was only visible from the traefik dashboard. Any routes where I had fail2ban as a middleware simply returned 404s.
Unfortunately since I skipped a minor version of traefik, it's not clear which had the breaking change: 3.6.14's forwardAuth middleware changes, or 3.6.15's new headers added to the Errors middleware.
Either way, I had to remove the plugin from any routes it was attached to, after which they worked fine.
I recently upgraded my k3s traefik deployment from 3.6.13 to 3.6.15, and discovered the the fail2ban plugin was silently failing; its failure was only visible from the traefik dashboard. Any routes where I had fail2ban as a middleware simply returned 404s.
Unfortunately since I skipped a minor version of traefik, it's not clear which had the breaking change: 3.6.14's forwardAuth middleware changes, or 3.6.15's new headers added to the Errors middleware.
Either way, I had to remove the plugin from any routes it was attached to, after which they worked fine.