Message server not updating

I’m currently using 5.2.26

You need to update to 5.3.0 your in a very outdated version. No wonder 9000+ didnt work. It was not even part of that version.

ok thanks mate, I will … 5.3.0 is from April… is that the latest version ?

Go to sambapos.com latest version is there.

hey all, i wanted to bump this thread as i’m still having this issue.

I’ve done alot of investigation and have realised there were errors in my config, which i’ve corrected, but still not working.

So i have updated to version 5.3.0.
Set all of the clients to connect to “http://server
I’ve set the message server on the server to be port 9000+ and updated all of the clients accordingly.
All of the clients show green “connected”
however, i still don’t get updated entity states on my entity screen automatically.

I go to the graphQL interface by going to “http://server:9090” and get an error:
“message”: “Authorization has been denied for this request.”

I’ve set the services to use an admin login.
gone to http://server:9090/login and tried to enter sambapos/password
but i get an error saying “try again”

Anything else i can try would be appreciated.

Regards
Damian
i’ve gone to http://server:9090/login

9090 is not correct. It should be 9000 Also sounds like you may have a firewall or third party software interfering.

Message server works for hundreds of thousands of restaurants with various versions of windows. Its definitely something you have configured wrong… Hopefully we can help you figure it out.

lol, apologies… i have it configured for 9000, not 9090 … old tomcat work coming out there.

i agree that it’s definitely our config, just can’t seem to figure out why :slight_smile:

i have tried disabling the firewall on both the server and a client, but that doesn’t seem to effect anything.

In regards to the authorization error i’m getting, is there something i’m not doing right to address that ?


this is what i’m seeing

and the address shown above is the right address… i used “server” as an example when writing up the original note, but the clients are configured to connect to http://posserver:9000

I’m inclined to agree with Jesse about something blocking access to the message server port.

The GraphQL playground only works if you have setup the proper user and application access within SambaPOS.

From a remote terminal, see if you can open a telnet connection to the message server. If the port is open and accepting connections you should see something like this:

the clients are configured to connect to http://posserver:9000

Does posserver resolve on remote terminals?

1 Like

Yes you have to login first. The fact you get that message means it’s working.

Try the Same address with /login added and use the username you assigned access. Typically admin.

yep, i can telnet - that was the first thing i tried … see below:

so, this is what i’m missing - i haven’t assigned a user any access to the message server … is that just a standard user that is configured via user ?

also, yes, i can ping “posserver” fine on remote terminals without issue

the configuration I mentioned is only if you want to run queries/mutation directly from the web playground.

So, it looks like you’ve ruled-out connection issues.

Out of curiosity, if you disable the firewall on the terminal running the message server are you able to connect?

yep, tired that as well… disabled windows firewall on both client and server, but unfortunately, it doesn’t make a difference… i’m racking my brains with this one.

hey all,

I’ve worked this out, so thought I would update this thread in case anyone else has this issue.

Turns out that we had the ethernet port on the server configured as a “private” network - correctly - but some of the clients had their ethernet port configured as “public”.

While the firewall rules specifically allowed this traffic and we were always able to get connection to the server, the entity status updates weren’t happening in realtime until they were both on the same, in this case private, network.

That was incredibly frustrating to work out, but we got there. Hopefully this post helps some else out.

3 Likes