Plugin integrity check fails for github.com/fosrl/badger (Pangolin's plugin) v1.6.0 and v1.6.1

Traefik Traefik v3 (latest)
1

Hi,

I'm the maintainer of the Pangolin Badger plugin (GitHub - fosrl/badger: Traefik middleware authentication bouncer for Pangolin · GitHub). We're seeing Traefik fail to install v1.6.0 and v1.6.1 with a plugin integrity check error. v1.5.0 installs fine with the same setup.

Here's the error we get in Traefik v3.5 or later:

Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to install plugin badger: unable to check archive integrity of the plugin github.com/fosrl/badger: plugin integrity check failed"

Here is the plugin catalog page: Plugin

What we tried:

  • Confirmed download works for v1.5.0, v1.6.0, and v1.6.1 from plugins.traefik.io
  • Compared those zips to proxy.golang.org for the same versions
  • For v1.5.0, the SHA256 matched and /public/validate returned 200
  • For v1.6.0 and v1.6.1, the SHA256 from plugins.traefik.io did not match proxy.golang.org, even though the extracted contents looked the same
  • At one point /public/validate for v1.6.1 returned 404; later we also saw cached 200 responses that didn't seem to depend on X-Plugin-Hash, which made things a bit confusing to reproduce

Our best guess is that something on the catalog/validate side is unhappy with the 1.6.x archives (hash mismatch or stale cache), but we're not sure. We also wondered whether a retag of v1.6.0 could be involved, so we published v1.6.1 as a fresh tag, and that failed the same way.

Would someone be able to take a look at GitHub - fosrl/badger: Traefik middleware authentication bouncer for Pangolin · GitHub v1.6.0 / v1.6.1 on the plugin service?

Thanks!

2

If you think it’s a bug and it still persists, you could try reaching the developers at Github. Reference your post here.

3

Already opened an issue on traefik/picus last week. Do you suggest I open on one on traefik/traefik as well? Haven't received a response yet.

4

If Traefik is throwing the error, I would open an issue there. Reference other. The devs usually check traefik/traefik. Make sure to stress that it worked in old versions, fails on new.

Not sure what picus is, never heard of it, project description could be more telling, probably to find GitHub plugins for Traefik and list them in the directory.

5

Thanks. I opened an issue on traefik/traefik.

6

Looks like it was a bug on Traefik's side but it's all fixed. Thank you Traefik team! Details are in the GitHub issue.