:8998 connection closed error

[richard_newberry]

Please see attachment.

[HansR]

That can happen. Apparently this is on a mobile. Did you walk out of range?
Does reconnect work (refresh the page)?

[richard_newberry]

I got a wifi signal near the router.

Refreshing the page same error?

Only :8998 as the problem.

[Mapantz]

I've got the same problem..

However, the problem occurs on Samsung Internet browser for me, but not using Edge..

Seems to be just port 8998.. weird

[HansR]

Lack of interaction?

[freddie]

Maybe some browsers only permit web socket connections on port 80 or 443?

[richard_newberry]

Can this problem be sorted on all browsers please?

[Phil23]

I'd say it's a browser issue.

Samsung Galaxy S20+ here & I get exactly the same port error.
If I try it with Chrome it works fine.

Can't see where there is anything that could be fixed in CMX if Samsung's Browser is closing a connection to the port.
Maybe try running CMX on a different port & even test on port 80 as it always open (but I could be way wrong with that suggestion.

I've used Samsung's Browser for many years & have always considered it does a few strange things.
Caching maybe? But I've often found occasions where I needed to switch to Chrome for things to work.

Cheers.

[Phil23]

Maybe some browsers only permit web socket connections on port 80 or 443?

Googled "Android Browser websockets"....

Lots of hits indicating that there are various issues with support.