traefik: command traefik error: failed to download plugin github.com/BetterCorp/cloudflarewarp: error: 500
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?
Other Refs: https://github.com/traefik/traefik/issues/7358 - https://github.com/darkweak/souin/issues/209 - https://community.traefik.io/t/downloading-plugins-fails-with-client-timeout/8896
Spinning up an instance of traefik, with config and all defined as would be production: https://github.com/BetterCorp/cloudflarewarp/actions/runs/2782040700 https://github.com/BetterCorp/cloudflarewarp/actions/runs/2783000196
What did you see instead?
command traefik error: failed to download plugin github.com/BetterCorp/cloudflarewarp: error: 500
Ref: https://github.com/BetterCorp/cloudflarewarp/issues/12
What version of Traefik are you using?
2.8 - traefik:latest
What is your environment & configuration?
https://github.com/BetterCorp/cloudflarewarp/blob/master/test/traefik-prod.toml
https://github.com/BetterCorp/cloudflarewarp/blob/master/test/traefik-compose-prod.toml
If applicable, please paste the log output in DEBUG level
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (8 by maintainers)
Commits related to this issue
- Updated for https://github.com/traefik/traefik/issues/9225 - to v1.3.0 — committed to BetterCorp/cloudflarewarp by mrinc 2 years ago
- Cleaning up the amount of bash in the repo re: https://github.com/traefik/traefik/issues/9225#issuecomment-1203083085 — committed to BetterCorp/cloudflarewarp by mrinc 2 years ago
Thanks again @ldez !
We’re all good this side 😃
I cleaned our database, the scan will happen around 4:00pm (UTC)
In theory, you also have to add the retracted tags to the go.mod file: https://go.dev/ref/mod#go-mod-file-retract
It’s just informative but it can be useful.
Beware, you cannot recreate a previous tag, it’s related to Go proxy security. So you have to use new tags: don’t use v1.0.0
Oooooooh interesting!
Learn’t something new about go versioning today
Roger, think this is the best path to take 😃
Releases and tags nuked, will just clear and refresh the project
Thanks!