Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to configure for HTTP only? #87

Open
pepoluan opened this issue Feb 17, 2022 · 1 comment
Open

How to configure for HTTP only? #87

pepoluan opened this issue Feb 17, 2022 · 1 comment

Comments

@pepoluan
Copy link

pepoluan commented Feb 17, 2022

The reason is because, in my place of work, the SSL termination is already performed by the load balancer / gateway, so we really would like the Docker container to only respond to HTTP.

So, it is okay for Mattermost to insist that we access using https://mm.our.domain.com, but between the LB/GW and Mattermost, it really should be just plain HTTP.

I took a look at the included nginx.conf, and I'm not sure which lines I should 'merge' from the HTTPS server block into the HTTP server block...

@R8s6
Copy link

R8s6 commented Feb 17, 2022

I have pretty much the same setup as yours, with pfsense renewing & terminating SSL at the gateway level, and its HAProxy as the reverse proxy. Inside the LAN, i only need mattermost with http.

In your mattermost docker folder, edit the .env file, commenting out:

#HTTPS_PORT=443
#HTTP_PORT=80

A little down below, set APP_PORT= to your http port, which then gets fed to your reverse proxy.

Then instead of using docker-compose.nginx.yml, use docker-compose.without-nginx.yml:

sudo docker-compose -f docker-compose.yml -f docker-compose.without-nginx.yml up -d

Note: The docker-compose.without-nginx.yml still has ${APP_PORT}:8065, which is probably the default and no need to change it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants