Opening duplicate to get an answer

[svandive]

Fresh install of Pangolin on a brand-new VPS.

Pangolin log states Badger 1.3.1:
pangolin | 2026-06-27T19:19:32+00:00 [debug]: Verify session: Badger sent {"sessions":{"p_session_token_s.1781877380688":"zjuif3y2cyqcnfg6jny6mi55pumw73hv"},"originalRequestURL":"https://test.vandiver.dev/favicon.ico","scheme":"","host":"test.vandiver.dev","path":"/favicon.ico","method":"GET","tls":true,"requestIp":"174.169.163.162","headers":{"Accept":"*/*","Accept-Encoding":"gzip, deflate, br, zstd","Accept-Language":"en-US,en;q=0.9","Cookie":"p_session_token_s.1781877380688=zjuif3y2cyqcnfg6jny6mi55pumw73hv","Priority":"u=3, i","Referer":"https://test.vandiver.dev/","Sec-Fetch-Dest":"image","Sec-Fetch-Mode":"no-cors","Sec-Fetch-Site":"same-origin","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/27.0 Safari/605.1.15","X-Forwarded-Host":"test.vandiver.dev","X-Forwarded-Port":"443","X-Forwarded-Proto":"https","X-Forwarded-Server":"1f6e4822661f","X-Real-Ip":"174.169.163.162"},"badgerVersion":"1.3.1"}

traefik_config.yml configuration has the correct badger version listed

experimental:
  plugins:
    badger:
      moduleName: "github.com/fosrl/badger"
      version: "v1.4.1"

Why on a fresh install do I see badgerVersion 1.3.1 in the Pangolin logs when Traefik is configured for badger version 1.4.1?

[svandive]

So the issue is not that Badger isn't updating or is running the wrong version, but that the version.go file in the Badger source wasn't updated. The file version.go is still showing a version number of 1.3.1 even though the build has been updated.

Badger needs to be fixed.

[oschwartz10612]

Lets track in fosrl/badger#25