Is there any news on an upcoming chat app for 12b @hunterlester ? I missed out on TEST 12 ;-).
4 Likes
It works on 12b. I was trying it last night
1 Like
I loggen into my Laucher, started the win32-version but no luck. It hangs on what you see in the screenshot. The Launcher doesnāt pop-up for Authorization. When I close the Launcher and start the app it doesnāt work either (which I knew of course) but it does give an error about appendable data. So a different route than when the Launcher is active as it doesnāt give that error then. Wish I could help out here with some coding skills.
1 Like
Weird. It works for me on Win10 and Linux.Does the launcher log give any clues?
1 Like
Nope, I have no idea why itās not working.
Definitely worth to take a look. Can you choose what region to host it like digitalocean or is this standard with these vm providers ?
I think the more providers we use and the more countries is always more secure 
Last weekend I was trying digitalocean their scripting to boot droplets but had some issues with ssh. Next weekend or so when I have time Iāll try again.
1 Like
Got this error message after rebooting and starting vault again (after resource proof passed):
WARN 11:46:34.388880247 [routing::routing_table mod.rs:971] Some sections in the RT arenāt neighbours of our section: RoutingTable {
min_section_size: 8,
our_name: f60643ā¦ (11110110ā¦00101100),
our_prefix: Prefix(111)
section 0 with Prefix(111): {
e2f734ā¦ (11100010ā¦11101110),
e43246ā¦ (11100100ā¦11110110),
ec0618ā¦ (11101100ā¦01101000),
f3bfcaā¦ (11110011ā¦10100011),
f60643ā¦ (11110110ā¦00101100),
ec441fā¦ (11101100ā¦01001110),
e60e29ā¦ (11100110ā¦00111101),
ebfa63ā¦ (11101011ā¦00100101),
e9d63bā¦ (11101001ā¦10011011),
fc51c7ā¦ (11111100ā¦11110111),
f9725fā¦ (11111001ā¦00100001),
e2b98eā¦ (11100010ā¦11011001),
e47d9eā¦ (11100100ā¦11001101),
e4db31ā¦ (11100100ā¦01101100),
eff90cā¦ (11101111ā¦01000010),
f90fcdā¦ (11111001ā¦11001111)
},
section 1 with Prefix(110): {
},
section 2 with Prefix(1011): {
},
section 3 with Prefix(100): {
},
section 4 with Prefix(1010): {
},
section 5 with Prefix(0110): {
},
section 6 with Prefix(010): {
},
section 7 with Prefix(0111): {
}
merging: we false, they false
}
INFO 11:46:34.388886427 [routing::states::node node.rs:971] Node(f60643ā¦(111)) Received invalid prefixes in NodeApproval: RoutingTable(InvariantViolation). Restarting.
WARN 11:46:34.388934525 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 11:46:37.884326540 [routing::states::node node.rs:1240] Node(3a2bd5ā¦()) Requesting a relocated name from the network. This can take a while.
2 Likes
So, after deleting the files from public folder, and deleting the mapping of the dns. I can still access the index.html of test.aenemic (now strangely without being logged in also), but no subsites. But after deleting the sample.aenemic I cant access it at all. I get: {āerrorCodeā:-1004,ādescriptionā:āDnsError::ServiceNotFoundā}
A bit strange behavior no?
Thatās definitely a bug and we are currently looking into it.
It looks like section 110 wants to merge with 111 but not vice-versa, which should never be the case over a long period of time. We have a suspicion where the problem is and will soon tweak the merging logic accordingly.
We are even thinking of ways to nudge the live network into completing the stalled merge by restarting one or two droplets.
Anyway, thank you for pasting the error message! Itās helping us a lot!
10 Likes
I in particular liked the āmerging: we false, they falseā error message, haha.
3 Likes
Thatās just because your node wasnāt around yet when ātheyā (section 110) notified āusā (section 111) about their intent to merge.
4 Likes
I provided āalternative factsā, network called me out on it. Haha.
Edit, should also add, that after starting the vault over again, it connected no problem.
9 Likes
I guess it didnāt get a node name starting with e or f then.
Well as far as I can tell Maidsafe is actually completely finished and there is absolutely no reason to test it. #alternativefacts
3 Likes
Interesting (scratches head).
Any idea about my other issue?
I uploaded two different sites, the sample one at safe://sample.aenemic which works fine and also safe://test.aenemic - and this one only loads if Iām logged into launcher, whereas the other site only needs me to be connected through launcher. The error it throws me is:
{āerrorCodeā:-9,ādescriptionā:āCoreError::OperationForbiddenForClientā}
So, after deleting the files from public folder, and deleting the mapping of the dns. I can still access the index.html of test.aenemic (now strangely without being logged in also), but no subsites. But after deleting the sample.aenemic I cant access it at all. I get: {āerrorCodeā:-1004,ādescriptionā:āDnsError::ServiceNotFoundā}
Did you map a private dir as test.aenemic ? That would give you that outcome I think. Possibly a bug if so as perhaps we should not allow mapping private dirs as public data?
1 Like
Nope, it was in the public folder, (both sites where in the same folder anyway) and the DNS map said public. And stranger still, after deleting it I can now access the index.html without logging in. Although pressing any of the sublinks gives me the {āerrorCodeā:-1004,ādescriptionā:āDnsError::ServiceNotFoundā} error which is what the index also should give me after deleting the folder and DNS I would think.
1 Like
Hmm, that is strange and sounds like a bug. Perhaps @Krishna_Kumar can jump in here to get more info and try and reproduce that. So you had a dir with two sub dirs and mapped both sub dirs to different names to see this fault?
1 Like
No, directly inside the Public folder in the Demo App I had two folders, one for each site. One was mapped to sample.aenemic and worked fine for anyone, logged in or not. The other was mapped to test.aenemic and only worked for me, when I had logged in through launcher.
I tried remapping the DNS, didnt change anything.
Then I deleted the test.aenemic DNS map and the folder from Public, and now, without loggin in to launcher i can access it (without reuploading it), although only the index.html.
Then I deleted the sample.aenemic one and that one I cant access at all now(as expected).
Should have taken screenshots come to think about it, but ah well. The power of hindsight?
2 Likes
I gave it a try but Iām not reproducing it, after I deleted the folder (without deleting the mapped service) I get:
{"errorCode":-2,"description":"CoreError::UnsuccessfulEncodeDecode"}
Then, when I deleted the service I get:
{"errorCode":-1004,"description":"DnsError::ServiceNotFound"}
You cannot access any safe site without logging into the Launcherā¦, did you refresh the page after logging out of the Launcher and still able to access the page?? arenāt you just seeing the cached index.html page?
What were the complete urls, were they safe://sample.aenemic and safe://test.aenemic ? (note they are safe:// not http://).
1 Like