Hello @selsno - this is a minor bug in Go’s HTTP/2 implementation, which was fixed by one of our devs. It does not cause any functional defects, just an error log will be shown.
The fix will be included in Go 1.17 which is yet to be released. After which, we would need to include that in Mattermost.