You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
Prior to the launch of the official network, my nodes were running well, and earning regularly. After completing the upgrade process post-launch, ensuring I used the correct --rewards-address suffix (evm-arbitrum-one), my nodes are no longer able to connect to any other nodes at all. This has happened on two separate machines in the home, both running Arch Linux, one a fresh install of it.
Running Arch Linux
I use CLI usually, and usually --home-network is the only way I can get connections, and thus PUTs.
When it didn't work this time, I did a reset, deleted the ~/.local/share/autonomi directory, and the executables in ~/.local/bin etc, and tried node-launchpad also. Using launchpad, I tried each connection method (Auto, home-net, upnp, and manual ports), and tested each for more than an hour, with the same results.
I've confirmed that I'm behind a CGNAT (Starlink), that QUIC is able to operate over my connection, and have run nat-detection via antctl, which returns 'Private'.
I'm assuming something in the software has changed between the last pre-launch version and the post-launch one, as my setup worked fine before launch. The same thing happened earlier in the beta rewards period, for quite some I could not connect at all, but one of the updates solved the issue.
Hi there,
Prior to the launch of the official network, my nodes were running well, and earning regularly. After completing the upgrade process post-launch, ensuring I used the correct --rewards-address suffix (evm-arbitrum-one), my nodes are no longer able to connect to any other nodes at all. This has happened on two separate machines in the home, both running Arch Linux, one a fresh install of it.
Running Arch Linux
I use CLI usually, and usually --home-network is the only way I can get connections, and thus PUTs.
When it didn't work this time, I did a reset, deleted the ~/.local/share/autonomi directory, and the executables in ~/.local/bin etc, and tried node-launchpad also. Using launchpad, I tried each connection method (Auto, home-net, upnp, and manual ports), and tested each for more than an hour, with the same results.
I've confirmed that I'm behind a CGNAT (Starlink), that QUIC is able to operate over my connection, and have run nat-detection via antctl, which returns 'Private'.
I'm assuming something in the software has changed between the last pre-launch version and the post-launch one, as my setup worked fine before launch. The same thing happened earlier in the beta rewards period, for quite some I could not connect at all, but one of the updates solved the issue.
Log file from a single node included.
antnode.log
The text was updated successfully, but these errors were encountered: