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

Users become logged in to another user

$
0
0

Hi guys,

we are experiencing the same problem!

our system:
OS Server: SLES 11 SP4
OS Client: Windows 10 Enterprise 64 bit
Server: 5.7.1 (initially 5.1-> 5.4 -> 5.7.1)
Client: mostly mattermost desktop app 4.2.0/4.2.1, no browser

Sessions (LDAP/Mobile/SSO): 30 days
Session Cache: 10 Min

our mattermnost runs behind nginx. Configuration as described here:
https://docs.mattermost.com/install/config-proxy-nginx.html

Summary (exactly the same behaviour as descibed by Camille and Schrell):
User will become logged into another user’s account somehow, either over time or immediately after logging in.

all users were set up the same way.

after client start the user is automatically logged in as another user (sporadically!) so you can read the whole communication(posts/channels etc.) of the affected colleague.
sometimes it is enough to click on File -> Settings… -> server name and then you are magically logged in as another user

it is difficult to reproduce the issue because very offen it is working as expected.

the affected users have only one account. Our working stations are new and without “history” so there is only one user profile

currently there is only one workaround: “clear cache and reload” and then it just works.

There is nothing suspicious in the log and i have no guess what is going on and the project leads are getting nervous. :slight_smile:

Any Ideas for further investigations?

Thanks in advance

Roman


Apache reverse proxy to foreign server wss issue

$
0
0

Hi @qmor, Do you have any information in your Mattermost logs - around Wed Apr 24 16:01:03 2019 - why Mattermost refused that connection?

Websoket "posted" event not contains "file_ids"

No system console access

Websoket "posted" event not contains "file_ids"

Websoket "posted" event not contains "file_ids"

Android app is not working

$
0
0

I had a look.
I have checked everything
I have checked the ssl certificate and it says A Score.
So i don’t understand why it does’nt work . And why when i connect with demo.mattermost.org and i disconnect, then i can connect to my server…

Android app is not working

$
0
0

@Tony, Would you be able to test if you see the same issue on a more recent server version (our latest version is v5.10)?


Install on ispconfig Debian9 with docker =connection reset

$
0
0

Hi,

I have a server installed with ispconfig managing email, web sites, etc. it’s a debian 9. I try to install the lastest docker version on my server but I always get a connection reset when I try to connect to my server.

docker seems to be up :
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1bf906f6fb15 mattermost-docker_app “/entrypoint.sh matt…” 23 seconds ago Up 18 seconds (health: starting) 8000/tcp mattermost-docker_app_1
6bd5a9d4320e mattermost-docker_db “/entrypoint.sh post…” 23 seconds ago Up 17 seconds (health: starting) 5432/tcp mattermost-docker_db_1
12225c5d01fe mattermost-docker_web “/entrypoint.sh” 23 seconds ago Up 17 seconds (health: starting) 0.0.0.0:4433->4433/tcp, 80/tcp, 0.0.0.0:8065->8065/tcp mattermost-docker_web_1

I saw some people added iptables rules. I tried with no success. i tried a Nmap on my server, port 8065 doesn’t seem to listen.

i’m running out of ideas. Any help would be really appreciated

Install on ispconfig Debian9 with docker =connection reset

Install sur debian 9 ispconfig avec docker = connectin reinitialisée

$
0
0

Hello,
J’essaie d’installer mattermost sur mon serveur (quifonctionne deja pour le web, les mails , etc.)
l’install se passe bien mais quand je devrais pouvoir acceder à l’interface web, j’ai un “Connection reinitialisée”. J’ai essayé un nmap mais le port 8065 ne semble pas écouter.

pourtant, mattermost semble bien lancé :

$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6e65444d3e46 mattermost-docker_web “/entrypoint.sh” 5 minutes ago Up 5 minutes (healthy) 0.0.0.0:4433->4433/tcp, 80/tcp, 0.0.0.0:8065->8065/tcp mattermost-docker_web_1
a4beb26995fe mattermost-docker_db “/entrypoint.sh post…” 5 minutes ago Up 5 minutes (healthy) 5432/tcp mattermost-docker_db_1
4035883c483d mattermost-docker_app “/entrypoint.sh matt…” 5 minutes ago Up 5 minutes (healthy) 8000/tcp mattermost-docker_app_1

J’ai essayé d’ajouter des regles iptables mais soit je n’ai pas trouvé la bonne soir ce n’est pas le probleme. Quoi qu’il en soit, si qq1 a une idée, je suis preneur !

Android app is not working

$
0
0

Amy, I have installed mattermost via Qnap install button.

How can i update my version to the v5.10 ?

Thank you

Le mar. 30 avr. 2019 à 16:10, Amy Blais via Mattermost Peer-to-Peer Forum mattermost@discoursemail.com a écrit :

[solved] Apache reverse proxy to foreign server wss issue

$
0
0

looks like i’ve solved a problem. just need to redirect mattermost wss connection to 443 port not 8065

RewriteRule .* wss://192.168.3.230:443%{REQUEST_URI} [P,QSA,L]

instead of

RewriteRule .* wss://192.168.3.230:8065%{REQUEST_URI} [P,QSA,L]

No system console access

$
0
0

Hi Amy,

The config looks good, and works (as in the site works, just I get no SystemConsole)

https://mattermost.bybent.com/

I also get this:

Please check connection, Mattermost unreachable. If issue persists, ask administrator to check WebSocket port.

I’m using mattermost without a front end. mattermost is listening on 443, so all connections are direct.

No system console access


Community version, user privileges

$
0
0

I’m testing a community version of mattermost but I want to check how can I restrict privileges to staff members because right know every member that I have invited has the ability to add new members, create channels, delete channels and that is a deal breaker for us.

I have research in the forum but with no luck. Can anyone point me in the right direction?

Thanks in advanced.

Install on ispconfig Debian9 with docker =connection reset

$
0
0

@amy.blais Maybe

Hi @Chag, do you have any log messages from your containers ? On your snippet, I can see that all your container are in starting health state, meaning the application is not correctly running. Maybe you can found a log error message on one of the containers.

502 Bad Gateway

$
0
0

Oh I get it ! Someone came on Github with a similar issue, because he is using a Raspberry PI. I noticed that you are using an ARM version of Docker, so I assume you are running on an ARM device. The Mattermost Docker image is using the AMD64 binary.

I’m not sure Mattermost is working on ARM, maybe someone from the development team could answer on this.

Install on ispconfig Debian9 with docker =connection reset

$
0
0

Hi @pichouk,
the container is in starting mode because I restarted it. Few seconds later it was in running and healthy state. It looks like the container is ok but there’s some kind of problem with iptables. I’ll try to setup a very simple container with basic nodejs hello world to try to fbd the right network/iptables configuration

Community version, user privileges

Viewing all 25792 articles
Browse latest View live


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