Definitely not mine… I raise my nodes right! 
10 Likes
I’ve got tons of lines of:
ERROR 21:50:54.012200200 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.060706700 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.061706100 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.148218000 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.148218000 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.148718000 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.149717800 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
ERROR 21:50:54.292735500 [routing::peer_manager peer_manager.rs:1123] Node(e43246..(111)) Missing public ID for peer f15a9a...
It seems this should be requested of said peer, and if it isn’t received the peer should be removed no?
EDIT:
Just saw David’s post. I guess this is because the test net is shut down? Still seems strange it stayed as a peer so long.
1 Like
I don’t like you are all having fun running vaults from home while I cannot due to my low bandwidth, I will be definitely getting one of those AWS accounts for next testnet 
10 Likes
hmhmmm - i am afraid my node could be a little bit of a slowy -.-" 
but very cool something like that happened =) exterminating one bug after the other 
4 Likes
12B+ sounds right to me 
3 Likes
Any takers for a community net using binaries for test 12b?
Easy enough for using the free instance tier on aws
If not then we’ll wait for a later one or just use alpha 2 when it arrives
2 Likes
I do not really have time now but your aws solution is very interesting! I will certainly Use it to run a second free vault when network is live
1 Like
Will need an IP address for each node so it can be added to the crust config and launcher config files
Port forwarding will also have to be done as for test 12b
Add this line to your vault crust.config file and launcher config file You can remove all the other ip addresses.
“35.167.139.205:5483”,
“nn.nn.nn.nn:5483” <------ this is where you put your internet IP address (not the 192.168.0.xxx but the internet one
And change the network name to “user_network_12_b”
So your file looks something like
{
"hard_coded_contacts": [
"35.167.139.205:5483",
"52.65.136.52:5483",
"138.197.235.128:5483"
],
"bootstrap_whitelisted_ips": [],
"tcp_acceptor_port": 5483,
"service_discovery_port": null,
"bootstrap_cache_name": null,
"network_name": "user_network_12_b"
}
EDIT: added new nodes to list And be sure to change the network name
2 Likes
Wont one bootstrap IP be enough for such a relatively small community test network?
Set the first flag and give us the IP.
See post above the first node is up and running. The first IP is the first node.
We need your node IP address so that it can also be added to the seeds
Oops! That was fast. I’ll try to join now but no guarantees as my connection is borrowed and fluctuates.
Really we would need a few nodes to be successful
and if your speed is unreliable then prob best not to be a seed node
Right. Futile anyway since ports are locked. Will have to speak to admin tomorrow. 
Others will no doubt step in if a new vaults test isn’t released within a 48 hours or so. That’s the beauty of this community. 
1 Like
I’ve joined you, my IP is:
"52.65.136.52:5483"
Node name is Node(c20076..()), peer ID: PeerId(45d080be..).
3 Likes
Can you remain online and if so then people can add your IP address to the config files
Yep, I’ll keep my node online!
3 Likes
See! See what I mean! Even Maidsafe developers just roll in smooth as butter and say I’m here, let’s get this going. Priceless. 
2 Likes
Add mine to the mix. “138.197.235.128”
4 Likes