@jrichards wrote:

I'm a first-time user with Mattermost, and am trying to install it. I am following the instructions on https://docs.mattermost.com/install/install-ubuntu-1604.html#configuring-mattermost-server. I have successfully installed it and am able to invite other team members to join the team. However, my main issue now is that in the address bar above, instead of saying "Secure" in green, it says "Not Secure" in red with a slash through the https part. I'm just not sure how to fix this. I'm sure it's a simple fix, I'm just really new to this.

Posts: 2

Participants: 2

Read full topic

@marouane wrote:

Hi all,
I installed mattermost server in my machine and i want to link it to tuleap,
My objective is the user can sign in to tuleap team by add the tuleap url and can find all tuleap team members and can doing discussions with them.
Any one have an idea about a solution for that.

Posts: 1

Participants: 1

Read full topic

@pruthvip wrote:

Installing on MAC OSx.

running make run is throwing the following error

[EROR] Failed to ping DB retrying in 10 seconds err=Error 1045: Access denied for user ‘mmuser’@‘localhost’ (using password: YES)

Posts: 2

Participants: 2

Read full topic

@iFEARR wrote:

Hello, Im using apache as the proxy for mattermost, but I can’t get it work
I get :

ws://chatdomaincom/api/v4/websocket
Request Status Code:500 Internal Server Error

Here it is my configuration.

ServerName chatdomaincom
  ServerAdmin hostmaster@mydomain.com
  ProxyPreserveHost On


  setup the proxy
  <Proxy *>
         Order allow,deny
         Allow from all
  </Proxy>

  Set web sockets
  RewriteEngine On
  RewriteCond %{REQUEST_URI} ^/api/v4/websocket [NC,OR]
  RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR]
  RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
  RewriteRule .* wss://127.0.0.1:8065%{REQUEST_URI} [P,QSA,L]
  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
        # This line simply forces HTTPS
  #RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]

  <Location /api/v4/websocket>
        Require all granted
        ProxyPass ws://127.0.0.1:8065/api/v4/websocket
        ProxyPassReverse ws://127.0.0.1:8065/api/v4/websocket
        ProxyPassReverseCookieDomain 127.0.0.1 chatdomaincom
  </Location>

  <Location />
        Require all granted
        ProxyPass http://127.0.0.1:8065/
        ProxyPassReverse http://127.0.0.1:8065/
        ProxyPassReverseCookieDomain 127.0.0.1 chatdomaincom
  </Location>

Posts: 1

Participants: 1

Read full topic

@jorge wrote:

I have pulled the mattermost-webapp, mattermost-docker and mattermost-server and successfully made some changes locally.

I also tried to deploy the mattermost docker to AWS Elastic beanstalk, but my question is: How can I deploy my local changes to AWS?

I do not have much docker knowledge so I think the documentation does not cover what I need. But I believe I am quite close to the deployment. Can anyone at least give me some direction on it? Thanks.

Posts: 1

Participants: 1

Read full topic

@kjkeane wrote:

This guide is to provide an introduction on installing, configuring and utilizing HAProxy as a proxy for Mattermost. This is just the way I have HAProxy currently configured, so if there are any issues with this guide please leave a comment and I will do my best to update it.

HTTP/2 support is coming to HAProxy in version 1.8

    frontend www-https
     bind *:443 ssl crt /etc/haproxy/certs/{domain-name}/{domain-name}.pem alpn http/1.1,h2
     mode http

Installing HAProxy Server

In a production setting, use a proxy server for greater security and performance of Mattermost.

The main benefits of using a proxy are as follows:

• SSL Termination
• HTTP to HTTPS redirect
• Port mapping :80 to :8065
• Standard request logs

To install HAProxy on Ubuntu Server:

1. Log in to the server that will host the proxy and open a terminal window.

2. Install HAProxy.

   sudo apt-get install haproxy

3. After the installation is complete, verify that HAProxy is running.

   sudo systemctl status haproxy

Note:

You can stop, start and restart HAProxy with the following commands:

  sudo service systemctl stop haproxy
  sudo service systemctl start haproxy
  sudo service systemctl restart haproxy

What to do next

1. Map a fully qualified domain name (FQDN) such as mattermost.example.com to point to the HAProxy server.
2. Configure HAProxy to proxy connections from the internet to the mattermost Server.

Configuring HAProxy as a proxy for Mattermost Server

HAProxy is configured using a file in the /etc/haproxy/ directory. You need to edit the haproxy.cfg file. When editing the file, you need the IP address of your Mattermost server and fully qualifed domain (FQDN) of your Mattermost website.

To configure HAProxy as a proxy

1. Login in to the server that hosts HAProxy and open a terminal window.

2. Open the file /etc/haproxy/haproxy.cfg as root in a text editor and add the following lines at the end of the file. Make sure that you use your own values for the Mattermost server IP address and FQDN for server_name.

   frontend www-http
   bind :80
   mode http
   default_backend mattermost
   
   backend mattermost
   mode http
   server 10.10.10.2:8065 check
   

3. Restart HAProxy

   On Ubuntu 14.04 and RHEL 6.6: sudo service haproxy restart

   On Ubuntu 16.04, Debian Jessie, and RHEL 7.1: sudo systemctl restart haproxy

4. Verify you can see Mattermost through the proxy.

   curl http://<mattermost_server>

If everything is working, you will see the HTML for the Mattermost signup page.

5. Restrict access to port 8065.
   By default, the Mattermost server accepts connections on port 8065 from every machine on the network. Use your firewall to deny connections on port 8065 to all machines except the machine that hosts HAProxy and the machine that you use to administer Mattermost server. If you’re installing on Amazon Web Services, you can use security groups to restrict access.

Now that HAProxy is installed and running, you can configure it to use SSL, which allows you to use HTTPS connections and the HTTP/2 protocol.

Configuring HAProxy with SSL

Using SSL gives greater security by ensuring that communications between Mattermost clients and the Mattermost server are encrypted. It also allows you to configure HAProxy to use the HTTP/2 protocol.

Although you can configure HTTP/2 without SSL, both Firefox and Chrome browsers support HTTP/2 on secure connections only.

You can use any certificate that you want, but these instructions show you how to download and install certificates from Let’s Encrypt, a free certificate authority.

To configure SSL:

1. Log in to the server that hosts HAProxy and open a terminal window.

2. Install git.

   If you are using Ubuntu or Debian:

   sudo apt-get install git

   If you are using RHEL:

   sudo yum install git

3. Clone the Let’s Encrypt repository on GitHub.

   git clone https://github.com/letsencrypt/letsencrypt

4. Change to the letsencrypt directory.

   cd letsencrypt

5. Stop HAProxy.

   On Ubuntu 14.04 and RHEL 6.6:

   sudo service haproxy stop

   On Ubuntu 16.04 and RHEL 7.1:

   sudo systemctl stop haproxy

6. Run netstat to make sure that nothing is listening on port 80.

   netstat -na | grep ':80.*LISTEN'

7. Run the Let’s Encrypt installer.

   ./letsencrypt-auto certonly --standalone

When prompted, enter your domain name. After the installation is complete, you can find the certificate in the /etc/letsencrypt/live directory.

8. Open the file /etc/haproxy/haproxy.cfg as root in a text editor and update the server section to incorporate the highlighted lines in the following sample. Make sure to replace {domain-name} with your own domain name, in 2 places.

   frontend www-http
   redirect scheme https code 301 if !{ ssl_fc }
   
   frontend www-https
   bind *:443 ssl crt /etc/haproxy/certs/{domain-name}/{domain-name}.pem
   default_backend mattermost
   

9. Restart HAProxy.

   On Ubuntu 14.04 and RHEL 6.6:

   sudo service haproxy start

   On Ubuntu 16.04 and RHEL 7.1:

   sudo systemctl start haproxy

10. Check that your SSL certificate is set up correctly.

• Test the SSL certificate by visiting a site such as https://www.ssllabs.com/ssltest/index.html
• If there’s an error about the missing chain or certificate path, there is likely an intermediate certificate missing that needs to be included.

11. Configure a Let’s Encrypt backend

    backend letsencrypt
    server 127.0.0.1:54321
    

12. Restart HAProxy.

    On Ubuntu 14.04 and RHEL 6.6:

    sudo service haproxy start

    On Ubuntu 16.04 and RHEL 7.1:

    sudo systemctl start haproxy

13. Open the file /etc/letsencrypt/renewal/{domain-name}.conf as root in a text editor and update the http01_port section to incorporate the highlighted lines in the following sample.

    http01_port = 54321
    

Run a --dry-run so nothing gets renewed.

  sudo certbot renew --dry-run

14. Create a script called renew.sh to renew and generate a .pem for HAProxy.

In the following script, use your own domain name in place of {domain-name}

  SITE={domain-name}

  # move to the correct let's encrypt directory
  cd /etc/letsencrypt/live/$SITE

  # cat files to make combined .pem for haproxy
  cat fullchain.pem privkey.pem > /etc/haproxy/certs/$SITE.pem

  #reload haproxy
  service haproxy reload

Make the script executable

  sudo chmod u+x /usr/local/bin/renew.sh

15. Configure cron so that the certificate will automatically renew every month.

    crontab -e

In the following line, use your own domain name in place of {domain-name}

``@monthly /usr/bin/certbot renew --renew-hook "/usr/local/bin/renew.sh" >> /var/log/haproxy/cert-renewal.log``

Posts: 2

Participants: 2

Read full topic

@mpeltier wrote:

Hi,
I have using mattermost team edition 4.4.2 on centos 7 behind squid proxy. This config seems to be supported (https://github.com/mattermost/mattermost-server/issues/6469) but how could I tell mattermost to use the proxy? I have tried to set the HTTP_PROXY variable in /etc/systemd/system/mattermost.service and then to restart the service, but the HTTP_PROXY variable seems to be ignored. I have tried with and without proxy authentication (does Mattermost support proxy requiring authentication?)
Thanks in advance for your help,

…
[Service]
Environment="HTTP_PROXY=http://user:pass@proxy.domain.org:3128/"
Type=simple
WorkingDirectory=/opt/mattermost/bin
User=mattermost
Group=mattermost
ExecStart=/opt/mattermost/bin/platform
PIDFile=/var/spool/mattermost/pid/master.pid
LimitNOFILE=49152
…

Posts: 1

Participants: 1

Read full topic

@Ameliawilson wrote:

I recently installed the open-source Slack alternative Mattermoson a personal t2.micro Ubuntu instance in AWS. So far, I love it and thought I would share my experiences in using EC2, RDS, and S3 to host the application.

Mattermost has their own install guidewhich is pretty thorough and very helpful. By using a db.t2.micro RDS instance (free tier!) as the database server, it actually simplifies many of the steps.

1. Launch an Ubuntu instance in EC2. While it launches…

1. Launch a PostgreSQL RDS instance. Make sure to take note of the master username and password you specify. In the database options, name the database “mattermost”.

2. Verify that you have the correct inbound/outbound settings for your EC2 and RDS instance security groups.

Your EC2 instance will of course need to have inbound ports 80/443 open as well as 22 for SSH from your IP only.

80/443 are open to update the server. 485 is open so Mattermost can send emails over SMTP. 5432 is open only to the database’s security group.

Your RDS instance will only need inbound access on 5432 from the security group of the EC2 instance.

1. In a terminal window or with Putty, SSH to your EC2 instance and create a new user such as ‘mattermost’ with limited privileges

Example:

sudo useradd mattermost -m

sudo passwd mattermost

1. Referencing the Mattermost install guide, download the Mattermost server by typing
   wget [https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz](https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz)
   where X.X.X is the latest Mattermost release version.

2. Unzip the Mattermost server by typing tar -xvzf mattermost-team-X.X.X-linux-amd64.tar.gz

3. At this point in the install guide it mentions creating a location on the server for storing files. We’re hosting this on AWS, so let’s use S3 instead! Go ahead and create a new S3 bucket. S3 buckets need a globally unique name so do something like <your-domain-name>-mattermost-media. We will reference the bucket later in the configuration.

4. You may want to create a user with its own access key in IAM at this point that only has access to the S3 bucket you’ve created. You’ll need this access key in order for Mattermost to read and write to the bucket.

5. Use your favorite text editor to open ~/mattermost/config/config.json and once again reference the install guide (Step 7) to make the necessary modifications.

Under the DataSource replace mmuser and mmuser_password with the credentials you specified during the creation of your PostgreSQL RDS instance.

Again, under the DataSource replace 10.10.10.1 from the install guide with the endpoint address for your RDS instance.

Save and close the file, we’ll make some more changes later in the admin console.

1. Follow steps 8 & 9 in the install guide to test and start the Mattermost server. Once you’re up and running, login to the Mattermost server and navigate to the System Console.

2. Under File Settings in the System Console, change Store Files In to Amazon S3. Add your Access Keys that have permissions to the bucket you created earlier. Add your bucket name and specify the region it sits in (e.g. us-west-1). Save your settings.

3. Another AWS service we can utilize is SES in order to send emails to users. Under the SES service, click on Domains and walk through the steps in order to verify your domain name. This should involve configuring the DNS settings for your domain name and adding a TXT entry. I use Google Domains but you could also use Route 53 for yet another(!) AWS service in this guide.

4. Once AWS has verified your domain, click on SMTP Settings and create your SMTP credentials. If you’ve already done this before, you can use your existing credentials.

5. In the Mattermost system console, update your Email Settings to look like this:

smtpsettings.PNG1244x924

Note that your SMTP Server may be in a different region than mine.

1. At this point you should have a Mattermost server running on an EC2 instance with a PostgreSQL RDS instance and an S3 bucket for file storage!

If you run into any roadblocks or if something seems unclear, please comment below.

Source: www.cameronezell. com

Update 1/9/2017:

I’d like to thank reader Rob for providing me with the following insight: He was using a postgresql RDS instance like myself, but had issues starting Mattermost via systemctl until he removed all postgres dependencies mattermost.service from systemd. If anyone else runs into a similar issue, give this a shot!

Posts: 1

Participants: 1

Read full topic

@Franco wrote:

Hi,

after migration from V3.10 to mattermost-team.4.4.0, I stuck with integration of matterpoll-emoji (matterpoll-emoji-v0.1.0-linux-x86_64.tar.gz).

The error msg is:

grafik.png1296x125 14.2 KB

The only log messages I see are:

[2018/01/04 10:42:00 CET] [DEBG] websocket.read: closing websocket for userId=guz8ymianin1fyxgnx6a36gqba error=websocket: close 1006 (abnormal closure): unexpected EOF
[2018/01/04 10:42:01 CET] [DEBG] PUT - /api/v4/config
[2018/01/04 10:42:01 CET] [DEBG] Schedulers received config change.

Any ideas?

Tnx in advance,
Franco

Posts: 3

Participants: 2

Read full topic

@bizsupportdotca wrote:

I am following the instructions here: http://docs.mattermost.com/install/docker-ebs.html

Step 7 seems out of sync with the contents of GIT, as I get a 404 error on this page: https://github.com/mattermost/platform/tree/master/docker/

Posts: 1

Participants: 1

Read full topic

@Babbles wrote:

I would like to install Mattermost without using Docker using Plesk. I did not install it to /opt and installed under the site. ex: /var/vhosts/MAINSITE/mattermost/. I made all the settings and confirmed the initial function.

Create an account and confirm it by email. However, I can not set it up as a manager. I am waiting for someone’s solicitation. Perhaps I am missing the setting.
The big problem, however, is that SSL/TLS connection is not possible. Plesk incorporates the features of Let’s Encrypt. That is, I can not set Let’s encrypt obediently. I can not match the authority of Plesk’s certificate by installing it in / opt. By installing in the site, I can maintain the authority of Plesk’s certificate.
I am currently doing HTTPS connection itself. But I can not access Mattermost. Connection refused. This is the same even if I forcefully induce it in https in nginx.conf. I can use mattermost if I give up https. How can I use Plesk’s Let’s encrypt? I guess the setting method is incorrect.

If I enable Let’s encrypt and foward80to443 in config.json, it will be rejected if the 8065 port is waiting for a connection. How do I avoid this? Currently I set these to false. TLSCertFile and TLSKeyFile are “/usr/local/psa/var/certificates/CERTFILE”. Since I can not access SiteURL items by starting with https://, I am starting with http://.

Please help.

---

CentOS 7.5 / nginx 1.13.8 / MariaDB 10.1.34 / Plesk Onyx 17.8.11

Posts: 5

Participants: 2

Read full topic

@Babbles wrote:

If I enter all the URL address (http://mysite.com:8065) of my Mattermost site directly, I can use Mattermost normally. I want to make HTTPS connection but I can not use it.

First of all, I ignored Mattermost and confirmed the HTTPS connection at index.html on the site. Neither problem.
http://mysite.com/index.html -> OK
https://mysite.com/index.html -> OK
*Of course, redirect from http to https is also OK.

Next using Mattermost. Direct input URL.
https://mysite.com:8065

Firefox:

An error occurred while connecting to mysite.com:8065. SSL received a record that exceeded the maximum permissible length. error code: SSL_ERROR_RX_RECORD_TOO_LONG

Because we could not verify the authenticity of the received data, we could not display this page.
Please contact the website administrator for this issue.

Chrome:

ERR_SSL_PROTOCOL_ERROR

Next I set proxy_pass at the location of nginx.

location {
...
   proxy_pass http://localhost:8065;
}

In this case, it falls into a (redirect) loop.

location {
...
   proxy_pass https://localhost:8065;
}

In this case, the above SSL error.

I run ‘sudo -u mattermost /opt/mattermost/bin/mattermost’ and it seems that no errors are displayed even if I look at the situation.

my config.json:

“ServiceSettings”: {
“SiteURL”: “http://mysite:com”,
“WebsocketURL”: “”,
“LicenseFileLocation”: “”,
“ListenAddress”: “:8065”,
“ConnectionSecurity”: “”,
“TLSCertFile”: “”,
“TLSKeyFile”: “”,
“UseLetsEncrypt”: false,
“LetsEncryptCertificateCacheFile”: “./config/letsencrypt.cache”,
“Forward80To443”: false,
“ReadTimeout”: 300,
“WriteTimeout”: 300,
“MaximumLoginAttempts”: 10,
“GoroutineHealthThreshold”: -1,
“GoogleDeveloperKey”: “”,
“EnableOAuthServiceProvider”: false,
“EnableIncomingWebhooks”: true,
“EnableOutgoingWebhooks”: true,
“EnableCommands”: true,
“EnableOnlyAdminIntegrations”: true,
“EnablePostUsernameOverride”: false,
“EnablePostIconOverride”: false,
“EnableLinkPreviews”: false,
“EnableTesting”: false,
“EnableDeveloper”: false,
“EnableSecurityFixAlert”: true,
“EnableInsecureOutgoingConnections”: false,
“AllowedUntrustedInternalConnections”: “”,
“EnableMultifactorAuthentication”: false,
“EnforceMultifactorAuthentication”: false,
“EnableUserAccessTokens”: false,
“AllowCorsFrom”: “”,
“AllowCookiesForSubdomains”: false,
“SessionLengthWebInDays”: 30,
“SessionLengthMobileInDays”: 30,
“SessionLengthSSOInDays”: 30,
“SessionCacheInMinutes”: 10,
“SessionIdleTimeoutInMinutes”: 0,
“WebsocketSecurePort”: 443,
“WebsocketPort”: 80,
“WebserverMode”: “gzip”,
“EnableCustomEmoji”: false,
“EnableEmojiPicker”: true,
“EnableGifPicker”: false,
“GfycatApiKey”: “2_KtH_W5”,
“GfycatApiSecret”: “3wLVZPiswc3DnaiaFoLkDvB4X0IV6CpMkj4tf2inJRsBY6-FnkT08zGmppWFgeof”,
“RestrictCustomEmojiCreation”: “all”,
“RestrictPostDelete”: “all”,
“AllowEditPost”: “always”,
“PostEditTimeLimit”: -1,
“TimeBetweenUserTypingUpdatesMilliseconds”: 5000,
“EnablePostSearch”: true,
“EnableUserTypingMessages”: true,
“EnableChannelViewedMessages”: true,
“EnableUserStatuses”: true,
“ExperimentalEnableAuthenticationTransfer”: true,
“ClusterLogTimeoutMilliseconds”: 2000,
“CloseUnusedDirectMessages”: false,
“EnablePreviewFeatures”: true,
“EnableTutorial”: true,
“ExperimentalEnableDefaultChannelLeaveJoinMessages”: true,
“ExperimentalGroupUnreadChannels”: “disabled”,
“ImageProxyType”: “”,
“ImageProxyURL”: “”,
“ImageProxyOptions”: “”,
“EnableAPITeamDeletion”: false,
“ExperimentalEnableHardenedMode”: false,
“ExperimentalLimitClientConfig”: false,
“EnableEmailInvitations”: true }

I want to connect HTTPS by direct input at least. Please tell me how to make HTTPS connection with Mattermost.

Please help.

---

Mattermost: 5.1.0 / CentOS 7.5 / Nginx: 1.13.8 / PHP 7.1.20 / MariaDB 10.3.8

Posts: 4

Participants: 2

Read full topic

@Babbles wrote:

I tried and tried variously and Mattermost is installed and can execute it. I use PLESK to manage servers. This time I ignored PLESK and installed Mattermost, Mattermost worked fine. But I want to go through Plesk as much as possible. Because it is the existence of Let’s Encrypt. Plesk encompasses Let’s Encrypt.

---

I look at multiple conf files on a server using this Plesk, for example, I listen to 443 ports two or three times. So I think that trying to specify backend with nginx’s proxy_pass will cause a redirect error repeatedly.

PLESK Knowledge Database has the following guide.

location ~ ^/(?!.well-known).*$ {
proxy_pass https://127.0.0.1:8065;
port_in_redirect off;
}
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;

If I set this, it will result in NGINX’s “502 Bad Gateway” error. Even if I see the error log of NGINX. Pointed out that the version(5.1.12) of Passenger is old.

and

[error] 4389#0: *2 SSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol) while SSL handshaking to upstream, client: CLIENT-IP, server: SERVER-DOMAIN, request: “GET / HTTP/2.0”, upstream: “https://SERVER-IP/index.html”, host: “MATTERMOST-URL”

“Proxy_pass https://127.0.0.1:8065;” Just specifying this will stop my site. I can not even see Index.html (ignoring the 8065 port).

This is a unique way to deal with Plesk, but who knows?

NEXT.
I do not install Mattermost in /opt, and installing in the domain may cause Mattermost to work. However, in this case, it is judged as an invalid certificate and it is an error. I thought I could give Mattermost the authority of the certificate by putting Mattermost in the domain, but it seems not to be the case. However with this method 502 Bad Gateway error does not occur. SSL error or invalid error.

I have doubts about config.json. “ConnectionSecurity” “TLSCertFile” “TLSKeyFile” in ServiceSettings section. Let’s Encrypt is enabled on PLESK, so SSL is working. Add Mattermost to it. I do not seem to work unless I type some characters on those items. If I leave “ConnectionSecurity” blank, an error will remain in Mattermost’s log.

{"level":"error","ts":1533229598.2654252,"caller":"jobs/jobs_watcher.go:70","msg":"Error occurred getting all pending statuses: SqlJobStore.GetAllByStatus: We couldn't get the jobs, Status=pending, invalid connection"}
{"level":"info","ts":1533230153.655869,"caller":"runtime/asm_amd64.s:2361","msg":"http: TLS handshake error from CLIENT-IP:20575: EOF","source":"httpserver"}
{"level":"error","ts":1533233769.2149591,"caller":"jobs/jobs_watcher.go:70","msg":"Error occurred getting all pending statuses: SqlJobStore.GetAllByStatus: We couldn't get the jobs, Status=pending, invalid connection"}
{"level":"error","ts":1533243896.2961688,"caller":"jobs/jobs_watcher.go:70","msg":"Error occurred getting all pending statuses: SqlJobStore.GetAllByStatus: We couldn't get the jobs, Status=pending, invalid connection"}
{"level":"error","ts":1533251112.7517698,"caller":"jobs/jobs_watcher.go:70","msg":"Error occurred getting all pending statuses: SqlJobStore.GetAllByStatus: We couldn't get the jobs, Status=pending, invalid connection"}

What I would like to do is to stop the function of activating SSL on Mattermost’s side. Is this possible?

Posts: 1

Participants: 1

Read full topic

@Babbles wrote:

I select “iOS / Android application” in the item “Enable mobile push notification” on the system console. At this time “http://push-test.mattermost.com” is displayed in the “push notification server” item in a state that can not be edited.

When my Mattermost site is HTTPS connected, does Mattermost encrypt it to access http://push-test.mattermost.com? Is it the same when using on a PC?

Posts: 4

Participants: 2

Read full topic

@Babbles wrote:

I experienced a server malfunction, I reconstructed the environment. Mattermost is also similar. I am planning to build it in the same condition as before. However, I also encountered a certificate problem this time.

When I access Mattermost, Mattermost seems to be requesting a certificate of the original domain.

My mattermost is ’ mattermost.example.com’, and access it.
mattermost is not a certificate of “mattermost.example.com” but it requires a certificate of “example.com”.

Errors by web browser.

[CHROME] NET::ERR_CERT_COMMON_NAME_INVALID

[FIREFOX] SSL_ERROR_BAD_CERT_DOMAIN

I abandon the use of example.com and I assign example.com a certificate of mattermost.example.com to example.com. Then I will be able to access Mattermost.
And I can not log in. The error is as follows.

Invalid or expired session, please login again.

Even if I set a wild card certificate of * .example.com.

When I installed Mattermost for the first time, there was no such thing. At that time it was whether the certificate could be used or not. I am restoring Mattermost (including config.json) from the backup file. I am not using backup data in the environment reconstruction of the server.

How do I inherit the certificate of it when I access mattermost.example.com?
The setting in nginx.conf is the contents in Mattermost’s manual. The certificate uses Let’s Encrypt (external).

---

CentOS 7.5 / nginx 1.13.8 / PHP 7.1.23

Posts: 2

Participants: 1

Read full topic

@Babbles wrote:

I want to change Favicon. There is no favicon now.

When searching favicon in this forum, the following topics were selected.

Does the current situation have since changed since then?

Depending on the web browsers I use, when I access Mattermost, the Favicon of my server I use may be set. Even if I can not set my original Favicon, I want to change it to Mattermost favicon at least.

Posts: 2

Participants: 2

Read full topic

@byronquiroz wrote:

Hello,

I have a question, I want to mount Mattermost, it is an open source program that I can install in a vps, in the company we have a vps and we have more web hosted in this, my questions is how should I do to install this program in the mattermost domain. tibu.cl. Should I access another server, install it directly to the server or domain?

Posts: 2

Participants: 2

Read full topic

@rakeshbalguri wrote:

Hi all,

I am trying to install Matter most on Windows 10 with Docker and MySQL as a database.
I tried many options but still it fails with the following error.

The following is the command I am using to start Mattermost:

docker run --name mattermost -d --publish 8065:8065 -e MM_USERNAME=‘root’ -e MM_PASSWORD=‘mysql’ -e MM_DBNAME=‘mattermost’ -e DB_HOST=‘127.0.0.1’ -e DB_PORT_NUMBER=3306 -e MM_SQLSETTINGS_DRIVERNAME=‘mysql’ -e MM_SQLSETTINGS_DATASOURCE=‘root:mysql@tcp(127.0.0.1:3306)/mattermost?charset=utf8mb4,utf8&readTimeout=30s&writeTimeout=30s’ mattermost/mattermost-prod-app:5.5.1

The docker container starts and continues to throw this error in the logs

~ $ tail -f logs/mattermost.log
{“level”:“info”,“ts”:1544630762.8168886,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630762.8177576,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}
{“level”:“info”,“ts”:1544630772.8179853,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630772.8183506,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}
{“level”:“info”,“ts”:1544630782.8186,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630782.8187604,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}
{“level”:“info”,“ts”:1544630792.8189068,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630792.8190837,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}
{“level”:“info”,“ts”:1544630802.8192677,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630802.8195567,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}
{“level”:“info”,“ts”:1544630812.8197072,“caller”:“sqlstore/supplier.go:209”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1544630812.8202488,“caller”:“sqlstore/supplier.go:221”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:3306: connect: connection refused”}

I am able to connect o mysql with userid root and passowrd mysql. So connection to the database is not an issue.

I have spent too much time on this and now struck

Any help in resolving this is appreciated.

Thanks
Rakesh.

Posts: 2

Participants: 2

Read full topic

@pierre wrote:

Hello,
I clean installed node(v11.9.0) and npm (6.5.0) and launched “make run” to build run mattermost server & webapp but I get this error:

ERROR in ./root.jsx
Module build failed (from ./node_modules/babel-loader/lib/index.js):
SyntaxError: /home/pierre/go/src/github.com/mattermost/mattermost-webapp/root.jsx: Unexpected token (55:8)

53 | function renderRootComponent() {
54 | ReactDOM.render((

55 |
| ^
56 |
57 | <Route
58 | path=’/’

Can’t get it working, tried to change node/npm version to lower but didn’t work either .

Posts: 2

Participants: 2

Read full topic

@sparkplug wrote:

Hi,

I just tried installing the Docker image on the latest version of Docker for Windows according to the instructions and it failed with the error message Error response from daemon: Unrecognised volume spec: invalid volume specification: './mattermost-data'.

See command line output below:

>docker run --name mattermost-preview -d --publish 8065:8065 --add-host dockerhost:127.0.0.1 mattermost/mattermost-preview
Unable to find image 'mattermost/mattermost-preview:latest' locally
latest: Pulling from mattermost/mattermost-preview
6ae821421a7d: Pull complete
a9e976e3aa6d: Pull complete
e3735e44a020: Pull complete
bfd564e9483f: Pull complete
df705f26e488: Pull complete
0c5547f73d62: Pull complete
f437382cf8a1: Pull complete
4f22805bb6d6: Pull complete
394f0f652697: Pull complete
fb068b9b9d1f: Pull complete
fdfc96ad0937: Pull complete
886a6212b9f0: Pull complete
1e96655722a9: Pull complete
b365baa15224: Pull complete
133fe2c903bf: Pull complete
096da92e1724: Pull complete
16be38d85c42: Pull complete
2173d14092cf: Pull complete
3cb91b442d2f: Pull complete
Digest: sha256:c877090d67fdfe20d14b319f7dd0974c78b0c26f36b9f19460932ecbb5af9f78
Status: Downloaded newer image for mattermost/mattermost-preview:latest
docker: Error response from daemon: Unrecognised volume spec: invalid volume specification: './mattermost-data'.
See 'docker run --help'.

>docker version
Client: Docker Engine - Community
 Version:           18.09.1
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        4c52b90
 Built:             Wed Jan  9 19:34:26 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.1
  API version:      1.39 (minimum version 1.24)
  Go version:       go1.10.6
  Git commit:       4c52b90
  Built:            Wed Jan  9 19:50:10 2019
  OS/Arch:          windows/amd64
  Experimental:     true

Posts: 1

Participants: 1

Read full topic