"No teams are available to join", how do I create one?

Is that Websocket connection necessary to access the system console?

I added

  - ""

to docker-compose.yml and I am able to access the system console when connecting via port 8065.

Hi @herzkerl, in general Websockets are integral to how Mattermost works, and shouldn’t be disabled. Sounds like you are now able to access the System Console - please let us know if you encounter any other issues.

Hi @amy.blais and @pichouk, it seems like Websockets are needed to access system console. (Could you confirm?)

As stated in this thread on the Plesk forums, I added the following configuration to my Nginx config for that subdomain within Plesk:

location ^~ /api/v4/websocket {

	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
	proxy_set_header Host $http_host;
	proxy_set_header X-Real-IP $remote_addr;
	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

	proxy_set_header X-Frame-Options SAMEORIGIN;
	proxy_pass http://159.xx.xx.xx:32xxx;

I am now able to access Mattermost via subdomain without any ports—and the system console works, too.

Now, is there any need to get rid of the web container as proposed in the Production Docker deployment for Mattermost? If recommended, I’d like to connect to the app container directly.

Hi @herzkerl, Yes, websockets are needed for Mattermost to work properly.

pichouk will be able to help with the question on the web container.

Sure, web container is not mandatory. If you have your own web server you can directly bind your web server to the application container port 8000.

You can find an example of Nginx configuration for Websocket on the web configuration file. The configuration you paste should be ok as long as the proxy_pass directive redirect to the Mattermost application container.

Thank you very much! :slight_smile: