Connection Reliability Improvements

We've made infrastructure improvements to help instances stay connected to the Management Console more reliably.

Some users have experienced instances appearing "offline" in the Management Console even though the instances were running correctly and processing data. This was caused by network interruptions that the legacy communicator couldn't recover from automatically.

What We've Done

• Backend servers are now more stable, reducing connection interruptions.

Preview: Try the New FSMv2 Communicator

If you've been experiencing connection issues (instances showing offline when they're actually running), you can try our completely rewritten communicator which has better recovery from network interruptions.

To enable, add to your config.yaml:

agent:   communicator:     useFSMv2Transport: true

Or via environment variable:

docker run -e USE_FSMV2_TRANSPORT=true ...

To verify it's working, exec into your container and check the logs:

docker exec -it  sh grep fsmv2 /data/logs/umh-core/current

You should see log entries with fsmv2 and states like Syncing or TryingToAuthenticate.

Note: To disable later, you must explicitly set useFSMv2Transport: false` in config.yaml.

We'd appreciate feedback on how this works for you. Once validated, FSMv2 will become the default communicator.