Quantcast
Channel: Mattermost Discussion Forums - Latest posts
Viewing all 25517 articles
Browse latest View live

Desktop Application Notification sound not working

$
0
0

Hello @wget,

Thank you very much for your input.

What I’ve done:

  • updated Windows 10 to the latest version of 1809 build 17763.437. Double check that the settings in Windows Notification and Settings were not changed.
  • Killed the Mattermost process, uninstalled Mattermost desktop application, backup the data in %AppData%/Mattermost (just in case), deleted all content of inside the Cache folder, then reinstalled the latest v4.2.1 desktop application.

After trying these, I was still unable to hear any sound notification. I am not sure what other debug logs/info I should look into to find the root cause of the problem. Any ideas?


Jitsi (Plugin) within Mattermost

Server worked until I enabled TLS and LetsEncrypt

Docker Compose Mattermost with nginx Proxy dont work

Cannot open interactive dialog

Cannot open interactive dialog

$
0
0

I am using mattermost community 5.8 & 5.9
Both version do not work

Docker Compose Mattermost with nginx Proxy dont work

$
0
0

first thanks for you reply.

i see the link and i read the link, but is the doc real or outdatet.

i read thats mattermost 5… the port is now 8000 and not 8065. The docker app container say also 8000. So now i ám confused.
Also when i expose ports in the config file, always is come thats blocked not ended.

To my understand.

Port is 8065?
I bind my nginx proxy to 127.0.0.1:8065?

sry too much frustration and i think it is my fault :slight_smile:

Server worked until I enabled TLS and LetsEncrypt

$
0
0

Thank you I will see what this reveals.


Docker Compose Mattermost with nginx Proxy dont work

HipChat import of channel did not import into channel

$
0
0

I’ve hit that limitation of Hipmost aswell. One could argue, that the representation of a room with less than 8 people is a direct channel in Mattermost. Coming from Hipchat though, I don’t think that makes sense.
I have a local branch of Hipmost where I’ve fixed some issues. After realizing there is too many issues and some data not being migrated, I’ve created my own migration script. You can find it here: https://github.com/ergon/migratemost

Web Layer for security

[solved] Server worked until I enabled TLS and LetsEncrypt

$
0
0

Ok found my issue. My apache2 would keep persisting after being disabled and now mattermost can listen on both 80 and 443 so TLS is working as it did before.

Docker Compose Mattermost with nginx Proxy dont work

$
0
0

Hi @Felix,

Why did you bind your app container port 8000 to 443 ?

ports:
- “8000:443”

I think you should use port 8000 instead. Mattermost service is not listening on port 443 if you use the Docker image.

Desktop Application Notification sound not working

$
0
0

Please login with a new user to your pc. Same problem?

Google MFA breaks Golang bot startup


Docker Compose Mattermost with nginx Proxy dont work

$
0
0

Hi pichouk,

that expose was from one test. I set it now again from scratch but also , ist has always error 500.

i post you my settings:

ubuntu , nginx, docker

docker-compose.xml

version: “2”

services:

db:
build: db
read_only: true
restart: unless-stopped
volumes:
- ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
- /etc/localtime:/etc/localtime:ro
environment:
- POSTGRES_USER=mmuser
- POSTGRES_PASSWORD=mmuser_password
- POSTGRES_DB=mattermost
# uncomment the following to enable backup
# - AWS_ACCESS_KEY_ID=XXXX
# - AWS_SECRET_ACCESS_KEY=XXXX
# - WALE_S3_PREFIX=s3://BUCKET_NAME/PATH
# - AWS_REGION=us-east-1

app:
build:
context: app
# uncomment following lines for team edition or change UID/GID
# args:
# - edition=team
# - PUID=1000
# - PGID=1000
restart: unless-stopped
volumes:
- ./volumes/app/mattermost/config:/mattermost/config:rw
- ./volumes/app/mattermost/data:/mattermost/data:rw
- ./volumes/app/mattermost/logs:/mattermost/logs:rw
- ./volumes/app/mattermost/plugins:/mattermost/plugins:rw
- ./volumes/app/mattermost/client-plugins:/mattermost/client/plugins:rw
- /etc/localtime:/etc/localtime:ro
environment:
# set same as db credentials and dbname
- MM_USERNAME=mmuser
- MM_PASSWORD=mmuser_password
- MM_DBNAME=mattermost
# in case your config is not in default location
#- MM_CONFIG=/mattermost/config/config.json


nginx site config

upstream mattermost {
server 127.0.0.1:8000;
}

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

server {
server_name xxx;

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;
proxy_read_timeout 600s;
proxy_pass http://mattermost;
}

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_pass http://mattermost;
}


docker ps:

mattermost-docker_db 5432/tcp
mattermost-docker_app 8000/tcp

i have delete the web config in docker-compose, because nginx proxy.

in my nginx log file:

failed (111: Connection refused) while connecting to upstream,

What did I miss? Thank you very much for your time and help. Felix

Docker Compose Mattermost with nginx Proxy dont work

$
0
0

My debt and excuse me for taking up your time. I set in the nginx the docker ip from mattermost_app and the the upstream is correct.

Thanks again for trying to help me! Felix

Docker Compose Mattermost with nginx Proxy dont work

$
0
0

You should keep this part I think :

ports:
  - “8000:8000”

I guess you can have something working with this docker-compose.yml

version: “2”
services:
  db:
    build: db
    read_only: true
    restart: unless-stopped
    volumes:
      - ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
      - /etc/localtime:/etc/localtime:ro
    environment:
      - POSTGRES_USER=mmuser
      - POSTGRES_PASSWORD=mmuser_password
      - POSTGRES_DB=mattermost

  app:
    build:
      context: app
    restart: unless-stopped
    volumes:
      - ./volumes/app/mattermost/config:/mattermost/config:rw
      - ./volumes/app/mattermost/data:/mattermost/data:rw
      - ./volumes/app/mattermost/logs:/mattermost/logs:rw
      - ./volumes/app/mattermost/plugins:/mattermost/plugins:rw
      - ./volumes/app/mattermost/client-plugins:/mattermost/client/plugins:rw
      - /etc/localtime:/etc/localtime:ro
    environment:
      - MM_USERNAME=mmuser
      - MM_PASSWORD=mmuser_password
      - MM_DBNAME=mattermost
    ports:
      - “8000:8000”

OAuth client_credentials

$
0
0

Mattermost allow client_credentials OAuth2 flow? (https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/)

When I try to do:

curl -i -H 'Content-Type: application/x-www-form-urlencoded' -X POST 'http://localhost:8065/oauth/access_token' -d 'grant_type=client_credentials&client_id=yck8zdobibdrdg63hha9mnkh6w&client_secret=i3udgcyc638ji8gg8jmtips1fr' HTTP/1.1 400 Bad Request Content-Type: text/html X-Request-Id: 8so69qjpijfudeudrkhnxe6mee X-Version-Id: 5.10.0.5.10.0-rc5.1d238412e7aa1c87115d25bf580d16e9.false Date: Mon, 15 Apr 2019 18:53:13 GMT Content-Length: 650

I get:

HTTP/1.1 400 Bad Request
Content-Type: text/html
X-Request-Id: cmo3qsqbx3yzbc57379fdbkwqr
X-Version-Id: 5.10.0.5.10.0-rc5.1d238412e7aa1c87115d25bf580d16e9.false
Date: Mon, 15 Apr 2019 21:39:46 GMT
Content-Length: 650

    <!DOCTYPE html><html><head></head>
    <body onload="window.location = '/error?message=invalid_request%3A+Bad+grant_type&amp;s=MEUCIFTaTapz983dRVjtXf-3MeS5mL7hUXhw68_3fWSTdXsLAiEAry-wDITMXwgWo6FezsvHU4LJq1I-uhnY_GCsd74iPGQ='">
    <noscript><meta http-equiv="refresh" content="0; url=/error?message=invalid_request%3A+Bad+grant_type&amp;s=MEUCIFTaTapz983dRVjtXf-3MeS5mL7hUXhw68_3fWSTdXsLAiEAry-wDITMXwgWo6FezsvHU4LJq1I-uhnY_GCsd74iPGQ="></noscript>
    <a href="/error?message=invalid_request%3A+Bad+grant_type&amp;s=MEUCIFTaTapz983dRVjtXf-3MeS5mL7hUXhw68_3fWSTdXsLAiEAry-wDITMXwgWo6FezsvHU4LJq1I-uhnY_GCsd74iPGQ=" style="color: #c0c0c0;">...</a>
    </body></html>

Pretty sure I am doing something wrong, just don’t know what

Trying to create an Authorization Bearer Token that is not bound to an user but an app to access the api, is this possible, I don’t want to use the admin credentials to do API calls like create user or add user to a team

Jira Plugin Failing to Post

Viewing all 25517 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>