Mattermost Peer-to-Peer Forum

There are no links to create a group and admin console


#1

Summary

There are no links to create a group and admin console, after the first authorization (see screens).
Links:
Create a new team
Go to System Console

Steps to reproduce

  1. Iinstall and configure Mattermost

  2. Go to page Mattermost

  3. Enter mail, login and password for first use

  4. Version number
    Mattermost Version: 5.5.1
    Database Schema Version: 5.5.0
    Database: mysql
    OS: 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux

  5. Steps to reproduce your issue
    See steps to reproduce

  6. Link to the documentation you’re using, noting the step where you encounter the issue.
    https://docs.mattermost.com/guides/administrator.html#installing-mattermost


#2

Hey @Shevchik - are there any other users on the system? You can return a list of users via this API call

https://api.mattermost.com/#tag/users%2Fpaths%2F~1users~1usernames%2Fpost

If there are, the very first user created would have been the System Admin, with permissions to create a new team and go to the System Console.

If you’re unsure how to use the API call to return a list of users, let me know. Moreover, if you lost access to the first user created on the system, and hence lost System Admin permissions, let me know as well. We can help you on both :slight_smile:


#3

Hello
I can reset the database and then it will be possible to create the first user again, who will be the administrator.
But that doesn’t solve my problem.

How to apply api I don’t know


#4

I reset database and go to the web-mattermost link.
https://test.mattermost.com/select_team
Enter the first account (e-mail, login and pass)
results:
getting a view page:


#5

Hi @Shevchik,

We would need more details on your config settings, but normally these settings should be enabled:

Also, the site URL should be set in System Console.


#6

My config.json you can download the following link:


#7

Hi @Shevchik,

Config settings look fine,

Can you help use this command to check if you’re a System Admin on the server: https://docs.mattermost.com/administration/command-line-tools.html#mattermost-roles?

If not, you can use this command to promote yourself: https://docs.mattermost.com/install/troubleshooting.html#lost-system-administrator-account.


#8

May be problem in this case?
Error in logs mattermost:

p/plugin.go:55",“msg”:“Plugin manifest could not be loaded”,“plugin_path”:"/opt/mattermost/plugins/jira",“error”:“open /opt/mattermost/plugins/jira/plugin.yml: permission denied”}
p/plugin.go:55",“msg”:“Plugin manifest could not be loaded”,“plugin_path”:"/opt/mattermost/plugins/jira",“error”:“open /opt/mattermost/plugins/jira/plugin.yml: permission denied”}

Also, I additionally noticed that it does not work out the web socket correctly:


#9

I executed the command
./mattermost roles system_admin user1
the problem remains


#10

Hi @Shevchik,

Please take a look at these troubleshooting sections to fix websocket issues:


#11

I have not once checked these settings
the problem remains


#12

Hi @Shevchik, were you able to resolve the websocket issues?


#13

no, the problem remains


#14

Hi @Shevchik,

Since you have specified a SiteURL, can you help try if removing the WebsocketURL helps? You don’t need to specify WebsocketURL because the browser will get it from the web page automatically.

If this doesn’t help, can you share your Mattermost server logs?


#15

Hi @amy.blais

I have a local domain for example: test.com
Subdomain created on domain: chat.test.com and worked on Nginx
On Subdomain chat.test.com created ssl certificate
I have a local network server where install mattermost (server name: 15-mattermost) and worked on Nginx (Nginx settings on 80 port to 8065)

Nginx chat.test.com proxies requests on second sever Nginx where install mattermost

Nginx settings on second server:

upstream backend {
server 10.0.3.15:8065;
keepalive 32;
}

proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=mattermost_cache:10m max_size=3g inactive=120m use_temp_path=off;

server {
listen 80;
server_name 15-mattermost;

location ~ /api/v[0-9]+/(users/)?websocket$ {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
client_max_body_size 50M;
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-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
client_body_timeout 60;
send_timeout 300;
lingering_timeout 5;
proxy_connect_timeout 90;
proxy_send_timeout 300;
proxy_read_timeout 90s;
proxy_pass http://backend;
}

location / {
client_max_body_size 50M;
proxy_set_header Connection “”;
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-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
proxy_read_timeout 600s;
proxy_cache mattermost_cache;
proxy_cache_revalidate on;
proxy_cache_min_uses 2;
proxy_cache_use_stale timeout;
proxy_cache_lock on;
proxy_http_version 1.1;
proxy_pass http://backend;
}
}

Mattermost config.lson:

{
“ServiceSettings”: {
“SiteURL”: “http://10.0.3.15:8065”,
“WebsocketURL”: “”,
“LicenseFileLocation”: “”,
“ListenAddress”: “:8065”,

the problem remains

amy.blais, Help Please…


#16

Hi @Shevchik,

Sorry for the delay - can you help try use chat.example.com as SiteURL, and nginx as server_name.


#17

Hello @ [amy.blais]

You can see error in URL:

What else can you try?

I reset the default settings for mattermost:
./mattermost reset

Please look at the error

Any ideas?

In Logs mattermost see:

{“level”:“error”,“ts”:1549983010.541055,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upgr
{“level”:“error”,“ts”:1549983010.5411358,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“k3ie5gfwnfy6dg3r7t7iee5kbw”,“ip_addr”:"
{“level”:“info”,“ts”:1549983010.5411656,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983013.6825545,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983013.682667,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“bapy6481h38xbjaqx3xny1jyqa”,“ip_addr”:“1
{“level”:“info”,“ts”:1549983013.6827252,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983018.662803,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upgr
{“level”:“error”,“ts”:1549983018.662909,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket”,“request_id”:“n8maimpaupy9tjcuo4d3c9idfe”,“ip_addr”:“1
{“level”:“info”,“ts”:1549983018.6629508,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983024.9159412,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983024.9160273,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket”,“request_id”:“53u9hmu8t7yqxp9efj7dtk5wua”,“ip_addr”:"
{“level”:“info”,“ts”:1549983024.9160664,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983033.0292296,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983033.0293427,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“rxwqjbqogpgmmrqpp83748wf5e”,“ip_addr”:"
{“level”:“info”,“ts”:1549983033.0293934,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983041.3389049,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983041.3390021,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“nbkwocaocf8ntr3ykeormh5wna”,“ip_addr”:"
{“level”:“info”,“ts”:1549983041.3390472,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983047.1626077,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983047.1627326,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“zykf31hrw7nnujkhp1qfkeqeco”,“ip_addr”:"
{“level”:“info”,“ts”:1549983047.1627748,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983053.2725215,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983053.2726164,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“pxyjz7uxo7gd5b14mhfo3pj96h”,“ip_addr”:"
{“level”:“info”,“ts”:1549983053.2726593,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1549983061.8201215,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in 'Upg
{“level”:“error”,“ts”:1549983061.8202262,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:”/api/v4/websocket",“request_id”:“t8pcedaufbgnbbrfcgfwmn7d5c”,“ip_addr”:"
{“level”:“info”,“ts”:1549983061.8202686,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}

Update mattermost for 5.7.1 error stay:

{“level”:“error”,“ts”:1550051271.101209,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upgr
ade’ header”}
{“level”:“error”,“ts”:1550051271.1013055,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“67eytdm6aj8h8eoc6brqt3yg5a”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051271.101367,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051274.2140353,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upg
rade’ header”}
{“level”:“error”,“ts”:1550051274.2141292,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“7zsoyrfbdjffmgiz5qoh5175xr”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051274.2141738,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051277.3918576,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upg
rade’ header”}
{“level”:“error”,“ts”:1550051277.391929,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“g4gmf1t9upbtpx7ptm9w6ypemo”,“ip_addr”:“1
0.120.1.103”,“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051277.3919704,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051280.51858,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upgra
de’ header”}
{“level”:“error”,“ts”:1550051280.5187154,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“9pctzmizqtgdbdezxrhknun46c”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051280.5187593,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051284.121695,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upgr
ade’ header”}
{“level”:“error”,“ts”:1550051284.1217883,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“d9dtghrwjiyw9gbu6m9rwi9x4w”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051284.121829,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051287.4874332,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upg
rade’ header”}
{“level”:“error”,“ts”:1550051287.4875324,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“d8iz7fximjfe5nrx9euitrwdhr”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051287.4875748,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051290.8894308,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upg
rade’ header”}
{“level”:“error”,“ts”:1550051290.8895178,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“dm1o1bcuqp89xm6ybqp548ccra”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051290.8895617,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}
{“level”:“error”,“ts”:1550051295.1714041,“caller”:“api4/websocket.go:28”,“msg”:“websocket connect err: websocket: the client is not using the websocket protocol: ‘websocket’ token not found in ‘Upg
rade’ header”}
{“level”:“error”,“ts”:1550051295.1714914,“caller”:“web/context.go:60”,“msg”:“Failed to upgrade websocket connection”,“path”:"/api/v4/websocket",“request_id”:“zn36qa8uziy1jyfrscox66x9sa”,“ip_addr”:"
10.120.1.103",“user_id”:“c4jarpqinjrhmfoswt5x3cyksw”,“method”:“GET”,“err_where”:“connect”,“http_code”:500,“err_details”:""}
{“level”:“info”,“ts”:1550051295.1715317,“caller”:“http/server.go:1102”,“msg”:“http: multiple response.WriteHeader calls”,“source”:“httpserver”}


#18

Solved the problem by removing the nginx configuration on the server where mattermost is installed.

But there was another problem:

  • mattermost app for OS Adnroid and iOS cannot connect to server Mattermost.
    There are no problems in Windows OS and app for windows.

Are there any ideas?


#19

ssl certificate is used correct / commercial


#20

Hi @Shevchik, can you help take a look at this section on our troubleshooting docs for tips: https://docs.mattermost.com/mobile/mobile-troubleshoot.html#i-keep-getting-a-message-cannot-connect-to-the-server-please-check-your-server-url-and-internet-connection.