That is a third AWS instance I have connected now. DUnno what was going wrong earlier but it appears reasonably stable now - as lonng as nobody tries any mega uploads.
Hopefully we can get some more non-AWS nodes connected in the next few hours and normal uploading service can resume and then I will be able to take a couple of these down to save the bill at the end of the month.
Ah that fixed it.
I was using this Release SAFE Launcher v0.10.1 ¡ maidsafe-archive/safe_launcher ¡ GitHub
I didnât realized there was a -dev
haha - i didnât know that either xD glad that it works now!
Itâs weird the date is off, âdec 2016â Made me assume it is wrong version.
krishnaIndia released this on Dec 1, 2016
strange - but good to have the correct link in the topic close to the config file now =)
Yep - we really need a page pointing folk to the latest versions of each app to be used with each network if/when they differ
Yeah but the link in the topic was wrong from my perspective because the date is two months off.
Not just that, the there are two different 10.1 versions. Whenever I look at my launcher files⌠10.1, I assume there are no changes. They failed on their part. It should be 10.2, 10.3, etc etcâŚ
Iâd write in and complain. Donât forget to demand your money back as well.
yeah we should have a (pinned) thread with infos about the current community network, a correct config file and a link to the compatible launcher - maybe closed so it doesnât get filled with questions ⌠just up-to-date correct info
I demand my money back in safecoins. lol
as an alternative i would offer you 5 thankscoin for your hassle that you canât spend (because of not-yet-implemented ownership-transfer)
safe://eeek.southside/
hiya,
am i missing something?
doesnât seem to be anyone to bootstrap tooâŚ
is anybody running?
rup
Yes itâs up. Routing table size is 13. What config file are you using?
lol⌠obviously the wrong one!!
can you pop me the latest?
also once its up iâll leave so the ip can be added as a bootstrap vault.
185.16.37.149
rup
No probs. I havenât tried starting again since yesterday though. Hopefully this still works
{
âhard_coded_contactsâ: [
â86.184.57.178:5483â,
â13.80.119.160:5483â,
â85.93.19.51:5483â,
â35.157.162.33:5483â,
â35.156.220.253:5483â
],
âbootstrap_whitelisted_ipsâ: ,
âtcp_acceptor_portâ: null,
âservice_discovery_portâ: null,
âbootstrap_cache_nameâ: null,
ânetwork_nameâ: âcommunity_network_feb_2017â
}
ah, network name has changedâŚ
now running with 14 peersâŚ
please add my ip to the list as it will be up now til something changes
{
âhard_coded_contactsâ: [
â86.184.57.178:5483â,
â13.80.119.160:5483â,
â85.93.19.51:5483â,
â35.157.162.33:5483â,
â185.16âŚ37.149:5483â,
â35.156.220.253:5483â
],
âbootstrap_whitelisted_ipsâ: ,
âtcp_acceptor_portâ: null,
âservice_discovery_portâ: null,
âbootstrap_cache_nameâ: null,
ânetwork_nameâ: âcommunity_network_feb_2017â
}
rup
Welcome aboard 8a5cb9!
thanks!!
anyone seen bluebird? he was my partner running vaults last yearâŚ
nice to put something backâŚ
rup
Didnât know a network was up yesterday so I tried with 10 droplets but couldnât bootstrap somehow.
Iâm now at work and try to join community network this evening.
Any idea what I did wrong?
- 10 droplets public ipâs:5483 put in hard_coded_contracts
- open firewall ports 5483 5484
- boot first vault with option -f
- same network name in config file for every vault
Now I see above that service_discovery_port is null ??