Traefik docker container keeps crashing

Hi
I run traefik 2.10.6 as a docker container on my Unraid server. After a recent upgrade, the docker container keeps stopping randomly. I checked the logs and it seems to repeat something similar to this before it crashes:

goroutine 210 [select, 2 minutes]:
runtime.gopark(0xc002103f90?, 0x2?, 0xc0?, 0x31?, 0xc002103f7c?)
runtime/proc.go:398 +0xce fp=0xc002103e28 sp=0xc002103e08 pc=0x44138e
runtime.selectgo(0xc002103f90, 0xc002103f78, 0x0?, 0x0, 0x0?, 0x1)
runtime/select.go:327 +0x725 fp=0xc002103f48 sp=0xc002103e28 pc=0x4518a5
github.com/patrickmn/go-cache.(*janitor).Run(0xc001e82920, 0x0?)
github.com/patrickmn/go-cache@v2.1.0+incompatible/cache.go:1079 +0x7d fp=0xc002103fc0 sp=0xc002103f48 pc=0xcf8f5d
github.com/patrickmn/go-cache.runJanitor.func1()
github.com/patrickmn/go-cache@v2.1.0+incompatible/cache.go:1099 +0x25 fp=0xc002103fe0 sp=0xc002103fc0 pc=0xcf9105
runtime.goexit()
runtime/asm_amd64.s:1650 +0x1 fp=0xc002103fe8 sp=0xc002103fe0 pc=0x4758a1
created by github.com/patrickmn/go-cache.runJanitor in goroutine 140
github.com/patrickmn/go-cache@v2.1.0+incompatible/cache.go:1099 +0xdb

Here is the complete log:

Anyone know how to fix this?Thanks in advance

Share your full Traefik static and dynamic config, and docker-compose.yml if used.

static: global: checkNewVersion: true sendAnonymousUsage: falseserversTranspor - Pastebin.com
dynamic: http: ## EXTERNAL ROUTING - Only use if you want to proxy something manuall - Pastebin.com

I don't use docker-compose.yml since it is a Unraid docker template container
Thanks

Try running without all the plugins, to see if it’s Traefik itself or a plugin.

Ok thanks, I'll give it a go. It's strange, when I search the go-cache error on google with relation to traefik, a few links relate to the simple-cache plugin which I have enabled. I've installed this plugin but had it commented out of my http entrypoint for the past few months. Can it still cause issues even if it is not applied to an entrypoint?

According to your config, it seems to be loaded as a middlewares, but it’s not assigned. I would assume it’s still loaded and processed, so it probably could create that error.