Plugin issue due to a bad nginx configuration Summary {"level":"warn","ts":1616599242.1224701,"caller":"api4/websocket.go:38","msg":"The HTTP version field was detected as 1.0 during WebSocket handshake. This is most probably due to an incorrect proxy configuration. Please upgrade your proxy config…

Small edit : this was before updating my configuration and mattermost. Here is what I have now: {"level":"info","ts":1618646597.9716687,"caller":"mlog/sugar.go:21","msg":"Stopping grumble server","plugin_id":"com.mattermost.mattermost-grumble-plugin"} {"level":"info","ts":1618646597.9718294,"calle…

[image] BCPG: This happens with the grumble plugin, when I’m trying to connect to the mumble server. It is certainly a problem with my nginx config: @BCPG Thanks for sharing the solution of this. :star_struck: :heart_eyes: :heart_eyes:

Not actually the solution, but the problem :sweat_smile:

Check changelog for version 5.33: Redirect WebSocket handshakes done with an HTTP version lower than 1.1 will result in a warning, and the server will transparently upgrade the version to 1.1 to comply with the WebSocket RFC. This is done to work around incorrect Nginx (and other proxy) configs th…

[image] vinci: WebSocket handshakes done with an HTTP version lower than 1.1 will result in a warning, and the server will transparently upgrade the version to 1.1 to comply with the WebSocket RFC. This is done to work around incorrect Nginx (and other proxy) configs that do not set the proxy_h…

Hi, @BCPG While I understand that we have been taking a peek at your NGINX config, would you mind sharing the output of the following command? cat /opt/mattermost/config/config.json | grep "TLSMinVer" For example, this is how it looks like on my end: ahmaddanial@mattermost:~$ cat /opt/mattermost…

[image] ahmaddanial: cat /opt/mattermost/config/config.json | grep "TLSMinVer" I got the same output as yours for the command. But when I try to change the proxy_http_version to 1.2, it says : nginx: [emerg] invalid value "1.2" in /etc/nginx/sites-enabled/mattermost:63

Just to be clear, I never suggested setting the http version to 1.2 (which as far as I know does not exist), I suggested 1.1 before reading the nginx config. At this point I’m not sure what the issue is.

Sorry, misunderstand here :sweat_smile:

Nginx and plugin issue

Troubleshooting

BCPG April 17, 2021, 2:59pm 4

Not actually the solution, but the problem

Topic		Replies	Views
HTTP Proxy Version 1.1 Troubleshooting	21	5128	April 1, 2021
Issue with websocket connection using nginx Troubleshooting	8	8886	October 20, 2015
WebSocket connection to failed（wss） Troubleshooting	0	1421	December 28, 2021
Upgraded from 3.7 to 3.8 broke websockets! help! Troubleshooting	27	5472	May 8, 2017
[SOLVED] The famous "Failed to upgrade websocket connection" Installation	4	12952	May 29, 2017

Nginx and plugin issue

Related topics