mattermost / mattermost/docker
x509: certificate signed by unknown authority
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 533
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NGINX deployment and the plugin OAuth request to /plugins/servlet/oauth/request-token, then inspect how the Mattermost container trusts the internal CA. Done means the GitHub or Jira plugin connection succeeds without the x509 unknown-authority error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker, nginx
- Domain
- infrastructure, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100