mattermost / mattermost/docker

HTTPS_PROXY / HTTP_PROXY?

Open
#76 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
533
Forks
284
PR merge metrics
No merged PRs in 30d

Description

Hello

We are behind an outgoing proxy, and I suspect Mattermost not being able to connect to stuff

For example, docker logs mattermost :

```
{"timestamp":"2021-12-15 23:58:50.950 Z","level":"debug","msg":"ERROR: sending request - Post \"https://pdat.matterlytics.com/v1/batch\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","caller":"log/log.go:184","source":"rudder"}
```

I remember with a previous version of Mattermost (https://github.com/mattermost/mattermost-docker), I had to somehow configure outgoing http proxy. I precisely modified the Dockerfile to recompile it.

Please, what's the solution here?

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's Dockerfile and configuration entry points for outgoing proxy settings, then compare them with the referenced mattermost-docker approach. Confirm the supported configuration path for HTTPS_PROXY and HTTP_PROXY and document or implement it so the reported outbound request can use the proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.