You are here
John Markey - Wed, 2024/07/31 - 17:29
Just finished installing Matters most as an LCX container. Getting (Please check connection, Mattermost unreachable. If issue persists, ask administrator to check WebSocket port.) Matter most website shows a fix/soliton for Docker but non for LXC. How do I go about fixing this issue?
Forum:
Did you try the Docker fix?
My first guess is that there is some specific privileged required to run inside a default unprivileged container.
I did a quick search for the fix you are referring to, but nothing jumped out at me as what you were referring to. So without knowing exactly what the Docker fix entails I can't be sure, but there are reasonable odds that it is relevant to the issue you're hitting.
For what it's worth, my testing suggests that our appliance works fine in a full VM (installed from ISO). If you could share the link you're referring to, I'll have a look ASAP and see if it makes sense in the context of LXC. Either way when I get a chance I'll have a quick look myself and see if I can reproduce the issue running under LXC.
As a complete aside, Docker and LXC are very similar containerization implementations. Docker actually started life as LXC - just configured a little differently. Over time they have somewhat diverged, but the main difference is still the use case, rather than the technology. As you likely know, LXC provides full OS containerization, so more or less has a full OS (with some exceptions which leverage the host). As you also likely know, Docker is usually used as single application containerization. However under the hood, Docker still includes an OS, it's just the minimalist possible OS to run the desired app - plus any other dependencies.
Mattersmost
I forgot tp post the link
Did you set the IP you're using as the "domain"?
When you went through the first boot questions, did you set the IP as the Mattermost "domain"? If not, then I reckon that's the issue.
From what I gather, Mattermost creates the websocket using the domain set at firstboot. Then the front end tries to connect to the websocket via the address used in your browser address bar.
For what it's worth, I fired up an LXC container and set a test domain of www.example.net. I then added a hosts entry on my local machine pointing to the server's IP. Accessing Mattermost in my browser via the URL set at first boot worked fine and I couldn't reproduce the issue you reported.
Then as per your note about using IP, I reset the Mattermost domain to be the local IP that my server was using (rather than an actual domain), restarted the services and that seemed to work fine too - no websocket errors.
Then it occurred to me that perhaps you had set a dummy domain on firstboot but were connecting in your browser via IP. Then BAM - when I connected to my server via anything other than the "domain" set (called "siteUrl" In Mattermost config) I could reproduce the issue.
So either add the domain to your local PC hosts file - pointing to the server's IP. Or change the domain/url that Mattermost is using to be the IP - and connect via that.
Let me know how you go.
I set the hostname as the IP
Awesome!
Awesome! I'm glad to hear that resolved the issue. You're welcome re the help - that's why I'm here. :)
As something of an aside, incidentally I was just speaking with a colleague about creating a doc page for appliances that require a domain or URL to be set. As you've discovered, many will sort of work if you connect via a URL other than the one set at firstboot. But all of them will have some level degree of problem. It just didn't occur to me that your issue was related to that same discussion...
Anyway, good luck with it all.
Mattermost socket error
Ok, I'll fire one up myself
Ok thanks John. As I noted, I was pretty sure that the issue was related to LXC, but clearly not. :(
Thanks for trying that and apologies that it didn't help at all. Could you please provide a link to the Docker fix you referred to in your previous post? Also ,it may be worth checking the Apache logs to see if anything jumps out.
Regardless, I'll look into it myself ASAP and hopefully I'll be able to reproduce the issue. Assuming that I can, I should be able to develop a fix. I'll post back once I have more info.
Add new comment