Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Follow GitHub username 301s when checking plugin integrity

Open
#68 11 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
backend

Research direction

Start by locating the plugin archive integrity check in the plugin-service repository and reproduce the failure with a GitHub repository URL that returns a 301 redirect. The change should follow the redirect during integrity checking and emit a warning about the URL change; verify that plugin loading continues and that unrelated plugins are not blocked.

Written by the indexing model from the issue text.

Description

kind/bug/possible
Welcome!
  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.
What did you do?

Following a username change for the maintainer of the DenyIP plugin, it caused Traefik to fail to load all plugins on next restart with:

unable to set up plugins environment: unable to check archive integrity of the plugin [github.com/kevtainer/denyip](http://github.com/kevtainer/denyip): plugin integrity check failed.

Whilst GitHub don't necessarily leave these 301s in place indefinitely, there is a period where it does so, and thus Traefik should follow these 301s when doing the plugin integrity check and output a warning that the URL has changed (Which can then be configured to be watched for in the user's monitoring tool of choice), so plugin users have time to update to a newer version of the plugin with the new URL.

Relevant issue on the plugin's GitHub repository.

What did you see instead?

Any IngressRoutes using any plugin as a middleware fail to apply successfully, causing applications to output a 404.

What version of Traefik are you using?

3.1.2

What is your environment & configuration?

Kubernetes on GKE.

Relevant (plugins) part of config (now corrected to the correct github URL):

- --experimental.plugins.jwt.moduleName=github.com/team-carepay/traefik-jwt-plugin
- --experimental.plugins.jwt.version=v0.0.11
- --experimental.plugins.traceid.modulename=github.com/trinnylondon/traefik-add-trace-id
- --experimental.plugins.traceid.version=v0.1.5
- --experimental.plugins.denyip.modulename=github.com/kvncrw/denyip
- --experimental.plugins.denyip.version=v1.1.0
If applicable, please paste the log output in DEBUG level

No response

Dominant language
Go
Stars
5
Forks
9
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from traefik/plugin-service

All issues in traefik/plugin-service

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.