setpill

@devinbinnie What exactly do you want to see? Logs from the "console" tab in chromium dev tools? From the refreshed or non-refreshed client? Assuming "console" tab in non-refreshed client -...

I'm not sure what there is to show... There's nothing new happening in the console tab after changing my connection. If I refresh, it would simply create a new websocket...

As in, I'm saying both console tab logs would look exactly the same... One simply has been done before the network change one after.

Interesting. No, I do not get a `websocket closed` line in the console when I trigger this with my own server. I will try to recreate on community.mattermost.com

I can confirm that I can reproduce this (browser client) on community.mattermost.com with the following steps: 1. Connect to community.mattermost.com with 2 clients (different browser tabs) 2. Create a DM...

Port mismatch might be addressed by setting the `Host` header in the reverse proxy. Unsure how to resolve the protocol mismatch; snipe-it seems to ignore the `X-Forwarded-Proto` header.

@snipe thanks for the link, I was indeed missing one of the headers mentioned there. However, setting that does not seem to work... Perhaps something else is wrong. Excerpt from...

Does it have something to do with the `HEADER_X_FORWARDED_AWS_ELB` in [TrustProxies.php](https://github.com/snipe/snipe-it/blob/d3a555ce91fd838e625d0bcdb75f31a79439936b/app/Http/Middleware/TrustProxies.php#L27)? I am selfhosting this, not using a cloud provider.

Delving a bit deeper, I realise that the reference there to `HEADER_X_FORWARDED_AWS_ELB` is entirely redundant; it is a bitwise OR of several constants set [by symfony](https://github.com/symfony/http-foundation/blob/7.1/Request.php#L45-L48). `HEADER_X_FORWARDED_AWS_ELB`, here, is defined...

#9179 potentially related