I was adding a new device in existing working S2S but it stuck on connectivity test even there was no changeto the main node.
I did not stop s2s before updating
During attempt to pass connectivity test old s2s was functional. Networks reachable
There was no option to stop existing s2s anymore and I decided to delete it and recreate
Deletion worked and old s2s stopped functioning but I still cannot create a new one. It fails instantly on connectivity test with when previously it was taking time
Whe opening s2s edit it shows 3 warning
"Device version is less than 3.026 " lowest I have is 3.216
I'm still seeing the same problem (I think). After editing the enrolled devices, and clicking next to the port testing phase it does one of two things:
Immediately goes to the S2S status screen but no data is ever sent. It selects a main node but will never connect after pressing start.
It fails the test and says no ports are open on any router. Ports are open and I have two routers on different external IPs that do and have been set as main node before.
I just tried to unbind one of my nodes. Now I can't get it rebound to goodcloud because I have no record of the serial. Apparently dropbear is broken on this unit and is always requesting a RSA key as well. I'm unable to login and obtain the serial. @bruce Do you have historical record of previous bound devices if I supply ID and MAC?
