Instance manager gone missing

[rc179]

I built a VM 3CX using the 3CX ISO, and configured the Instance Manager, no problem. I then build a second one and set them up as a failover pair. Later I was looking at Settings and noticed that the Instance Manager option wasn't there. But if I manually type in the URL, I can still change the settings and it does still show on my partnet portal.

Strange, and I'd like it to be working. I don't know if the setting disappeared when I set up failover or when I updated the 3CX.

I saw this https://www.3cx.com/community/threads/v16-0-2-910-instance-manager-missing.67908/ but in my case it was there and now isn't, and the VM should look like Intel hardware.

 

[JohnS_3CX]

Hi @rc179

That's correct. Once you enable Failover, instance manager stops.


https://www.3cx.com/docs/manual/pbx-management/#h.qfash562493e/

 

[rc179]

And yet there it is, still working, just the button is missing. And this would have been good to know before we sold the system, since we use instance manager to manager our systems.

 

[JohnS_3CX]

Yes, it is listed there in the instance Manager Page I linked.

We do hide the instance manager from the settings once failover is enabled, you might be seeing a cached version. Refresh the Settings page and the option should disappear.

 

[rc179]

It's not cached. if I user the url that goes to the instance manager settings I can chage the settings and it will be reflected inb the instance manager page on the partner portal.

Instance manager is important to anyone who want to keep an eye on there systems, like a partner, and those partners are exactly the people who will use a failover system, especially given what it takes to do failover in a private IP environment on your debian based system.

 

[YiannisH_3CX]

Hello @rc179

Thank you for reporting this. The design is to disable the instance manager when failover is enabled so the issue here is why it remains active.
We will investigate internally and see why this happens.

 

[rc179]

Hello @rc179

Thank you for reporting this. The design is to disable the instance manager when failover is enabled so the issue here is why it remains active.
We will investigate internally and see why this happens.

Please keep in mind that Instance manager is how we keep an eye on our systems, that's its intent and I would imagine that other partners also use it. It is a critical component and rather than disable it, have it active on the active PBX, so some level of monitoring is maintained.

What's the point of having a monitoring solution if it can't be used to monitor all systems?

 

[YiannisH_3CX]

The reason the instance manager must be disabled when failover is enabled is because the instance manager only sees the primary machine because the machines share the same FQDN. The implementation currently does not allow for failover machines sharing the same FQDN. We also want to remove the chance that the failover is triggered because the machine was rebooted via the instance manager.
I understand your point and why you want to use it (we also use it for the same reasons) but the current implementation does not allow it.