Cumulus Support

Steve, you may be aware but you cannot run multiple instances of MX on the same box. I was using a Pi.

You can change the web port of the second instance (I used 8999), but it tries to start using the same web sockets port (8002) and fails as it is already in use.

I see the port is coded into dashboard.js, so if it were to be configurable at some stage, I would have to edit that file as well.

Not to worry, I'll move MX2 back to the main server, and then try MX1 on the Pi again...

mcrossley wrote:I see the port is coded into dashboard.js, so if it were to be configurable at some stage, I would have to edit that file as well.

I guess dashboard.js could query the server for the websockets port, if it were configurable.

Steve, I am now running two instances of MX on the same server, I just incremented the ports by one for the second instance - works a treat, thanks.

No C1 running at all now.

I just incremented the ports by one for the second instance

Hello Mark -

I have one instance of MX up and running. I see the need to change ports for a second instance and think I have that half resolved using CumulusMX.exe - port 8988 - but how do I change the web socket port to, for example, port 8003. I bet you have a bat file or two to facilitate the start as well - any chance you might share.

George Wheelock

Hi George, you use the -wsport 8888 parameter to change the web socket port number on the second instance.

I am back to running a single instance on a rPi so no fancy batch scripts.