Chrome does not allow plugins to set custom headers in WebSocket connections.
https://issues.chromium.org/issues/40815149#comment23
Therefore, the WebSocket path "/api/v4/websocket" should be added to the documentation as a recommended whitelist entry.
https://docs.mattermost.com/deployment-guide/server/pre-authentication-secrets.html
The NGINX and Apache examples may also need to be adjusted.