[Solved] WebSocket Setup

[Pepe]

Hi - I’m new to the forum here - but using mattermost since some time on a very basic way. Just basic setup.
MY mattermost server is running on Ubuntu Linux 20.04.6 with mattermost 10.4.3 and database based on postgres (12.22) in the Mattermost Enterprise Edition with no license.

I just upgarded the system to this version. System is working as before - upgrade path is simple and nice - THX

Already since some time I’m getting the WebSocket meaasse as “Please check connection, Mattermost unreachable. If issue persists, ask administrator to check WebSocket port”. I followed already many post here and in the internet who faced the “same message”.

I tried to drill it down to a minium of complexity - but will need help to probably understand the basics better.

The “site-url” is “http://vmmm-rd1.privat-net.intranet” (see picture below):

The client and the server are in the same network - with now firewall in between or a firewall on the Ubuntu server. So all plain.

I noticed from an other popst, that the WebSocket URL has to be set manualy in the file “config.json” - and it should be the same as the “site-url” (please see below):

In an other post I noticed something about “Cors” setting - even if I don’t understand for what it is, but I added here as well the “site-url” as well (see below):

In the past - my understanding was that the right URL to use is “http://vmmm-rd1.privat-net.intranet:8056”. If I’m using these URL - Im getting quickly the RED banner.
If I’m using “http://vmmm-rd1.privat-net.intranet” without the port at the end - the RED banner is gone.

[Pepe]

But I’m also not sure if WebSocket is working correct or not

If I’m using the URL with the port number I can see in the browser WebSocket activities:

Plus the RED banner some time later.

Messages from the browser:

With a bit more details:

Before I forget - this is the Apache2 virtual host config (based on what has been recommended here in a document - as half official):

I’m happy about any feedback - but please keep in mind I’m not a PRO

[Pepe]

Sorry one more feedback from my end.
I did a test once again without the port and found this message in the browser console:

Is this the validation that WebSockets are working fine?

[rtfm98]

I have to look for it later, but I think the Websocket URL I configured is without any protocol (ws:// or wss://). The docs ( Environment configuration settings - Mattermost documentation ) don’t really tell the necessary format for this config option..

[Pepe]

Quick update on the Apache2 front. HTTP is now working fine within the local network - no WebSocket errors - but https is still a challenge (for tomorrow).
Lattest Mattermost config settings:

[Pepe]

Sometimes it is the last change that makes the difference - https is now also working within the local network (Proxy-settings and Mattermost server on the same system)

<VirtualHost *:443>
  # If you're not using a subdomain you may need to set a ServerAlias to:
  # ServerAlias www.mydomain.com
  ServerName vmmm-rd1.privat-net.intranet
  ServerAdmin webmaster@localhost
  # DocumentRoot /var/www/vmmm-rd1.privat-net.intranet-ssl

  # SSL Section
  SSLEngine on
  SSLCertificateFile /etc/ssl/certs/vmmm-rd1.privat-net.intranet-self.crt
  SSLCertificateKeyFile /etc/ssl/private/vmmm-rd1.privat-net.intranet-self.key

  # Set web sockets
  RewriteEngine On
  RewriteCond %{REQUEST_URI} /api/v[0-9]+/(users/)?websocket [NC]
  RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR]
  RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
  RewriteRule .* ws://127.0.0.1:8065%{REQUEST_URI} [P,QSA,L]

  <Location />
    Require all granted
    ProxyPass http://127.0.0.1:8065/
    ProxyPassReverse http://127.0.0.1:8065/
    ProxyPassReverseCookieDomain 127.0.0.1 vmmm-rd1.privat-net.intranet
  </Location>

</VirtualHost>

I used the config file already in the past - but it looks like that the changes in the mattermost config fixed it now.

I will check tomorrow if I can get is working as well from the internet.

[Pepe]

As mentioned yesterday - http and https is working (Apache2 proxy settings and Mattermost server are on the same system).

Now I added my central Apache2 revers proxy with the following proxy config:

(FYI: vmmm-rd1.privat-net.intranet is the Mattermost server with the local proxy settings)
All OK but still the RED banner from WebSocket with the same error message:

FYI: There is no firewall inside the local network

Who can assist to get also that last bit fixed?

[john.oliver]

Integrations configuration settings - Mattermost documentation may help

[Pepe]

@john.oliver : Thank you for the hint. I was not aware about the impact of the CORS settings. After changing it to * it worked:

May I have overseen it, but to see and to understand the relation between web-server settings, websockets and CORS is missing in you documentation - just my view.

Anyway - now the internal network and external network access is working without errors