x509: certificate signed by unknown authority

[FrankvdHorst]

Hi,

I'm having a problem with activating plugins. The moment for example when I want to connect the Github plugin (or Jira, or whatever I want to connect) I get the following error:

failed to get a connect link: Post "https://server:8443/plugins/servlet/oauth/request-token": x509: certificate signed by unknown authority

I am using NGINX from this deployment and have used the chain of certificates (so including the CA in the cert.pem file provided to NGINX). HTTPS is working great, but connecting to plugins unfortunately give the above message.

Does anyone know what I could do to make this error go away? I am using an internal CA within the corporate network.

PS: We are using Debian

Thanks for any ideas.

[Frank-vd-Horst]

ok, figured this one out.

As said I am using Debian as my operating system, but it seems that the Mattermost container doesn't share the certificate repository with the host operating system, unless you specify the volume mapping in the docker-compose.yml file like the following:

Under the Mattermost section in the docker-compose.yml specify the following:

volumes:
  - ${MATTERMOST_CONFIG_PATH}:/mattermost/config:rw
  - ${MATTERMOST_DATA_PATH}:/mattermost/data:rw
  - ${MATTERMOST_LOGS_PATH}:/mattermost/logs:rw
  - ${MATTERMOST_PLUGINS_PATH}:/mattermost/plugins:rw
  - ${MATTERMOST_CLIENT_PLUGINS_PATH}:/mattermost/client/plugins:rw
  - ${MATTERMOST_BLEVE_INDEXES_PATH}:/mattermost/bleve-indexes:rw
  - /etc/ssl/certs:/etc/ssl/certs:ro

I added the last line for a installation of Docker on Debian. The Certificate store in the Mattermost container (based on alpine) is in /etc/ssl/certs as specified in the volume mapping.

Hope this helps someone who is facing the same issues.

Thanks

Frank