That got things working! Thank you so much!
My knowledge of routing/crust is limited but I am gonna guess this is what is going on… I am guessing that by default, the SAFE Browser uses the number of vaults it can detect as the
minimum_section_size. If I run the
minimum_section_size equal to the number of active vaults everything works perfectly fine. Above this value it breaks… So it is almost like (without proper configuration) SAFE Browser sits and waits for say 4 acks (4 is the number of vaults running) but doesn’t receive them because the
min_section_size is set to 2 so only 2 acks are sent. Is this on the money?
Do I need to configure a Node.js/Electron app I am building to have a
abcde.routing.config too? My application exhibits the same behavior as the the browser before I included the
routing.config file. Tried it and sure enough, yes is the answer. Everything seams to be working now.
One thing I am noticing… The network really doesn’t seam to like me adding more vaults after I have written ANY data to the network (including an account). If I open two vaults, create an account, then add a third it stops responding to requests. If I start three vaults then create an account it works perfectly fine. Is this expected behavior or is something else wrong? Vaults leaving and joining seams to be a bit unstable is what I am experiencing. Maybe this is just where Maidsafe are in development though!