HTTPS_PROXY / HTTP_PROXY?

[Bibelo]

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!

[mrckndt]

@Bibelo the solution to what? The error message you've posted isn't fatal at all. Is every outgoing request failing? If so you need to configure this inside the container or on the docker host.

[Bibelo]

@mrckndt Thank you for your answer and sorry for my late reply.

By design, every request cannot go out. Configuring an outgoing proxy server is necessary, always have been in my organization, and have been in the previous version of MM I'm currently using. It's a standard feature you find in products.

My question then was how to add outgoing http/https proxy to the image. It's not as simple as exporting a variable.

It should be somewhere, either in the MM config files or as a docker variable in the docker-compose. I found no documentation about it, that's why I'm asking.

Thanks in advance for your help.

Edit : toned down

[bor8]

I have the same problem. Outgoing connections don't get through because the proxy has to be used for that (in my case).

[bor8]

This is a problem! I can't change settings in system console! I get

Received invalid response from the server.

when clicking Save and I think it is related to this proxy problem!

[mrckndt]

@Bibelo The documentation you're searching for is here. This needs to be applied to the proxy facing container (either Nginx or Mattermost). It should also work when a proxy is configured on the Docker host.

@bor8 a bit more information would be great but the above is true for you too if using an outgoing proxy.

[bor8]

Thanks, it worked, this error Received invalid response from the server. is gone! I still have problems with some plugins - but this is a "minor" problem.