I am using ant-node-manager to start the node. But seems the —no-upnp not passing to start the node. How to fix it?
Can you post the output of antctl --version
I’m on version:-
Autonomi Node Manager v0.13.0
Package version: 2025.5.1.2
and this command worked for me:-
antctl add --metrics-port 13001-13050 --no-upnp --node-port 12001-12050 --count 50 --rewards-address <redacted> evm-arbitrum-one
and I don’t think I’ve done an update of antctl since.
Note that I put --no-upnp near the start of the line. I had problems putting it further in. I think it has to go before the node ports are specified.
1 Like
I downloaded from GitHub latest release and run with —no-upnp, and checked with systemctl status antnode1.service , all failed and exec without —no-upnp unlike previous version.
look through the help antctl --help and see if its still there. If not then they seem to either have removed it or maybe it has changed, maybe to --upnp
Just a thought
1 Like
I have tried to start 300 nodes, just few ten nodes started with the —no-upnp that works well, but others just failed and those started without the —no-upnp and error exit saying upnp gateway.
I shouldn’t update the nodes to 0.4.0, all started failed just like that. Just few nodes started ok since with the flags. And all the failed are started without the flags 
Same issue happening to my network and vps, all started failed with the latest version. Reset and start again still the same…
I have tried forced version to 0.3.11, 0.3.10, after latest upgrade, all with the same issue. The latest antnode crashed something
I have own build version for RISCV that works fine both node and node manager
But all those release from officials for ARM, aarch64 not working properly. I am not sure what have changed on their side, not debugable, just behaviour.
Now more than 4500nodes down. Thanks for the official upgrade!
I build my own version of ant-node and ant-node-manager, seems fixed the issue. Thanks for your reply.
1 Like