[Solved] How to setup mattermost behind nginx proxy manager?

Troubleshooting
1

Hello,
how to setup mattermost whitout ssl behind nginx proxy manager that provide ssl certificate with lan forward over http? There is no clear explanation for the proxy and for mattermost.

2

I was able to get this to mostly work using NGINX proxy manager. The only thing that does not work is under system console > web server > Site URL, the Test Live URL does not work. Saying Test unsuccessful: This is not a valid live URL.

However, everything else works.

I think the problem is similar to the problem I’m having with ghost crm behind a reverse proxy. It’s something to do with the header being wrong, but so far I have not figured out the solution to this problem.

Here’s my setup on NGINX proxy manager.

image
image641Ă—704 18.7 KB

image

3

Hi, I just wanted to follow up on this. My hunch about the x-forwarded-proto header was incorrect. I was having a firewall issue that prevented the mattermost server from connecting to the nginx server. After that was fixed, the Test Live URL now works.

Here are my updated nginx server settings.

image
image641Ă—704 18.7 KB

image
image1161Ă—887 37 KB

image
image1148Ă—1388 62.6 KB

4

You’re an absolute gem for following up with these solutions/clarifications, Mike! Big cheers! :gem:

5

Unfortunately, it doesn’t work for me. I have configured the NPM exactly as described above. Websocket support is activated. Nevertheless, I keep getting the error on the website:

"websocket error websocket.js:112:24
error { target: WebSocket, isTrusted: true, srcElement: WebSocket, eventPhase: 0, bubbles: false, cancelable: false, returnValue: true, defaultPrevented: false, composed: false, timeStamp: 241070, ... }
websocket.js:113:24
[1702118709.42] Polling websockets connection for state: undefined"

It seems to have something to do with what is written here in the documentation: There is an extra location configured for the websocket URLs. But I have no idea how this can be configured in NPM. I tried to set it up via the “custom locations” tab in NPM, but that didn’t work either. Any idea how to get rid of these errors/warnings?

6

I ran into a similar situation when I was trying to configure my own server. The key for me was making sure Nginx was properly set up to forward requests to Mattermost over HTTP.

I found that editing the Nginx config file to include the right server blocks and making sure the proxy_pass was pointing correctly did the trick. Don’t forget to set the X-Forwarded-For and X-Forwarded-Proto headers, as they’re crucial for Mattermost to recognize it’s behind a proxy.

If you’re looking for a quicker solution or extra security while setting this up, you might want to Buy Private Proxy from LightningProxies. It helped me feel more secure and made testing a lot smoother.