[Solved] No text response from any built-in or plugin slash commands

Summary
Messages from slash commands do not appear when run.

Steps to reproduce
Run a built-in or plugin-provided slash command which creates a channel message.
OS: RHEL 8
Mattermost: 9.5.7
PostgreSQL: 15.7
Browser: Firefox 115+

Expected behavior
Slash commands are behaving weirdly in that they seem to work, but there isn’t any text output from them when run. For example /code creates nothing when sending the message, but does eventually show up on a page refresh as expected. Something like /settings creates a pop-up right away though.

I’ve been integrating an existing GitLab install as well and using the out-of-the-box GitLab plugin that comes with the version of Mattermost I installed. Running /gitlab connect just does nothing, but I was able to connect my account using the GitLab icon on the sidebar which created a separate login window to use. Something like /gitlab me also just does nothing onscreen, but /gitlab subscription add some/project works and I can see the subscription in the sidebar when the page is refreshed with whatever features I indicated. Upon connecting my account the plugin bot dumped the help message, but /gitlab help never recreates this message. Unlike with the built-in commands, the plugin messages do not show up on refresh.

Observed behavior
There don’t seem to be any relevant errors to draw from, the commands just seem to execute and then nothing happens. At one point I had a typo in a URL for a custom GitLab command which created errors when using it, but those disappeared once the typo was corrected. The only evidence I could see of these commands in the logs is a debug message saying that a command was executed when using the custom GitLab command.

Sorry, I know this isn’t a whole lot to go on. The majority of my issues are with the GitLab integration, but the builtins were acting oddly enough for me to want to see if there was any insight on a potential wider issue before going to the plugin team directly. Thanks for any help in advance.

The solution ended up being to enable websocket functionality on my reverse proxy.

Heya afrasc! Thank you so much for following up with the solution!