I’ve been working on some improvements to make sure this is always the case. I’ve seen an scenario where antnode upgraded and Formicaio didn’t notice it (in my case it upgraded it again automatically afterwards anyways). With upcoming release this shouldn’t happen in any scenario.
This is not even possible, antnode doesn’t allow that.
If instead of using /metrics, you use /metadata, you get the version number. So a simple call to this before attempting an upgrade of the node will save you. The value is antnode_version
It has been strongly stated they will not be doing that for the time being or forever
I wrote this to Autonomi Discord, but realized soon, that maybe this thread would be better:
Some of my nodes has a number of “observed network size” greater than the network size on the Autonomi homepage. At the moment the Autonomi homepage network size is 14200, which matches quite well the network size that Formicaio calculates from all of my 65 nodes, 13900. I’m not sure if that is an average of all the sizes my nodes report. But if it is, can it be a correct refelction of the network size?
One of my node reports the observed size as 18944. Can they observe the size as larger than it actually is? How does that happen? Do they see some nodes twice? I can understand how nodes could “see” less nodes than there actually is, but I don’t understand how they could see more.
It seems to me, that the highest observed network size should be closer to truth, than the average of many observations.
I don’t need to know how the “observation” works in a very detailed way, but it would be nice to hear a brief explanation for these numbers, that seem illogical to me.
Maybe it’s just semantics though? Maybe the network size is more “estimated” than “observed”?
Its the average of all your nodes that makes it more accurate. The larger the number of nodes running, the more accurate it is. I suspect running 200 to 300 nodes at minimum is bare minimum sample size needed for a more accurate view. Each node cannot obtain the same network size number, its a probablistic / heuristic calculation.
I am forgetting the details off it now.
The network size shown by Formicaio is the average of all the network sizes reported by active nodes.
In the Dashboard I’m seeing my 200 nodes as inactive, while looking at the logs they’re still running. Also within Ubuntu I can see all those processes still up and running. When looking at the logs within formacaio, they’re actively producing logs. Looks like a bug of some sort.
Yes, that’s a bug. It’s very likely the issue I mentioned about antnode natively upgrading and Formicaio not noticing/keeping track of them once that happens. I’ll be making a new release this week with a fix for that, in the meantime you can simply restart Formicaio and start the nodes again.
Formicaio version 0.7.5 has been released and it’s ready for installation across all supported platforms in native mode. Docker containers built with this new version, including for UmbrelOS and CasaOS, will be also published in the next few hours.
This version introduces the following general improvements and fixes:
Users currently running nodes in home-network mode (with version 0.5.x or earlier) shouldn’t upgrade to this new version as home-network is not supported neither in v0.6.x nor v0.7.x.
For those using UmbrelOS, note v0.7.x are not yet published on the official UmbrelOS app store, but only on the Formicaio community app store.
If this is your first time installing Formicaio, you can easily follow the installation instructions in the README.
Make sure that, after upgrading, you refresh the page of any instance of the Formicaio frontend/GUI you have open on a browser with Ctrl + F5.
I downloaded the 0.7.5, and run it from folder: formicaio-v0.7.5-x86_64-unknown-linux-musl
But when I check the “About”, I see:
And it doesn’t appear to…:
Have you tried hard-reloading the webpage with Ctrl+F5 ?
No, I didn’t, and that did the trick. Sorry, and thanks! But just to make sure, that produces different results from clicking the browser reload button?
@bochaco Now that the team has specifically mentioned they do not want us to manually upgrade the nodes I think it would be good to by default hide the upgrade node button (and maybe even a warning message for people attempting to upgrade them that they auto update and if not upgraded within 6 days they can manually do it and flag the team). But additionally, it would be amazing to have the node running version in the node list view to see at first glance which ones have upgraded already.
Your tool is rapidly becoming one of the most used ways to launch and monitor nodes so having some best practices for the network in there is probably going to be really helpful.
Edit: Also, are you confident the node version is always updated correctly? I’m seeing 3 of my 200 nodes that are still (or again) on version 0.4.13. I’m actually pretty sure they were all on 0.4.14 before so it looks like some may have downgraded themself.
Edit 2: I just checked the node version of a node showing 0.4.13 in the formaciao dashboard, but it’s running 0.4.14, that seems to be a bug with fetching the node version.
Edit 3: After some talks back and forward with Chriso on Discord (link to conversation: Discord ), it would be neat if we could add the next schedueled auto upgrade check. TLDR: by checking the logs for “Next upgrade check scheduled for” you’ll get something like “[2026-02-06T12:43:25.438415Z INFO antnode 473] Next upgrade check scheduled for 2026-02-09 13:50:43.438413112 UTC” which helps you track when the node will auto check for a upgrade. Once known there is a new version, it will schedule the update which looks something like this: “Node will stop/restart for upgrade at 2026-02-01 21:27:07.906383634 UTC”
That’s just a way to force the browser reload the latest version of a webpage from the server clearing its cached version.
A bug related to this was fixed in Formicaio v0.7.5, if you are using that version that shouldn’t happen. Try restarting one of the nodes to confirm the version Formicaio is seeing.
I was running 0.7.4, updated a little while ago. I’ll keep an eye out 
cheers
Formicaio version 0.7.6 has been released and it’s ready for installation across all supported platforms in native mode. Docker containers built with this new version, including for UmbrelOS and CasaOS, will be also published in the next few hours.
This release introduces the following improvements/features:
Upgrade button in list view: The upgrade button now appears on every upgradable node in list view.
Native-mode restart preserves running nodes: When Formicaio runs in native mode and the process is terminated with a kill signal (e.g. using kill -9 <PID> or tools like btop), you can restart Formicaio without stopping nodes that were already active. On startup, Formicaio will detect and continue tracking those running nodes. If Formicaio was otherwise stopped with Ctrl+C, nodes will be shut down as in previous versions.
Note: this improvement lets you upgrade Formicaio without stopping running nodes, a requested enhancement discussed some time ago:
Users currently running nodes in home-network mode (with version 0.5.x or earlier) shouldn’t upgrade to this new version as home-network is not supported neither in v0.6.x nor v0.7.x.
For those using UmbrelOS, note v0.7.x are not yet published on the official UmbrelOS app store, but only on the Formicaio community app store.
If this is your first time installing Formicaio, you can easily follow the installation instructions in the README.
Make sure that, after upgrading, you refresh the page of any instance of the Formicaio frontend/GUI you have open on a browser with Ctrl + F5.
Formicaio version 0.7.7 has been released and it’s ready for installation across all supported platforms in native mode. Docker containers built with this new version, including for UmbrelOS and CasaOS, will be also published in the next few hours.
This release improves observability across notifications/alerts, batch processing, and MCP server status visibility:
Users currently running nodes in home-network mode (with version 0.5.x or earlier) shouldn’t upgrade to this new version as home-network is not supported neither in v0.6.x nor v0.7.x.
For those using UmbrelOS, note v0.7.x are not yet published on the official UmbrelOS app store, but only on the Formicaio community app store.
If this is your first time installing Formicaio, you can easily follow the installation instructions in the README.
Make sure that, after upgrading, you refresh the page of any instance of the Formicaio frontend/GUI you have open on a browser with Ctrl + F5.
EDIT: Now it works with Brave too, but I’ll leave the below here, just in case. I didn’t do anything, except reloaded the page one more time. 
Doesn’t work for me with Ubuntu and Brave (which was just updated), but works on Firefox on the same machine.
This time I have done
Ctrl + F5several times. On the Terminal everything works, but the GUI doesn’t do anything, when trying to start nodes, and when clicking on the menus, they all lead just to front page.
This happened to someone some time ago with Brave as well, it must be the way Brave deals with caching I suppose. I was gonna suggest to check Settings > Privacy & Security > Clear browsing data or toggling the Shields off and on for the site, or test in a new private window.
IIRC I had to stop Brave and reload entirely.
It worked fine after a full Brave restart.
