Yeh, that would be helpful indeed. A run form cmd line with the --debug param should give more output (and a couple of new debug console windows for where it does work)
1 Like
Vaults is only needed for running your own local testnet. authd would be needed though yeh 
The CLI itself should not be required but as you note, it’s probably the simplest way to get authd atm and configure the shared vault access.
A lot of this will be handled by SNAPP (cli install / authd etc) eventually. But if you just dl the browser you’d still be left hanging, so we’ll probably have to reuse the same scripts in browser if nothing is found (as I think prompting to get SNAPP might just be a PITA if you only want to browser)
4 Likes
FAQ: Browsing is for free… why do I need authd? Can browser not default to connect unauthorized.
1 Like
Sorry, to be clear it does already default to an unauthorised connection. And so should work w/o authd installed (at least is working here. I’m not 100% sure if connecting to get updated bootstrap info is needed these days).
When webapps or browser need to store things, they’ll need permissions + therefore authd as well. So we’ll need to document that aspect, and distinguish between ‘browse’ (readonly) and ‘store’…
(cc @JimCollinson maybe something to mull over: I think clearnet ‘browse’ you expect websites to work. Here we have a ‘read only’ kind of distinction. I’m not sure how/where that’d affect other messaging, but this is one instance.)
6 Likes
Yeah, the expectation is/was that to browse the network, the user need only install the browser, and they are good to go.
Should they want to, say, save a bookmark, or make any PUTs such as commenting on a blog, they’d begin a flow to install SNAPP and log in / create an account.
8 Likes
tried the fresh install on windows 10 april update and … works !!!
5 Likes
I’m having the same issue. This is the output when I try starting the browser from the command line.
C:\Users\AG\AppData\Local\Programs\safe-browser>
%c02:17:03.350%c ›
%c02:17:03.356%c ›
%c02:17:03.357%c ›
02:17:03.360%c ›
02:17:03.361%c ›
02:17:03.363 ›
02:17:03.364%c ›
02:17:03.367%c ›
%c02:17:03.368%c ›
02:17:03.372%c ›
02:17:03.374 ›
02:17:03.375 ›
02:17:03.377%c ›
02:17:03.378 ›
02:17:03.379 ›
02:17:03.380 ›
02:17:03.383%c ›
02:17:03.385%c ›
02:17:03.388%c ›
02:17:03.389%c ›
%c02:17:03.390%c ›
02:17:03.392%c ›
%c02:17:03.393%c ›
02:17:03.535%c ›
02:17:03.536%c ›
02:17:03.538%c ›
02:17:03.543%c ›
02:17:03.544%c ›
(node:13260) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:13260) DeprecationWarning: file property is deprecated and will be removed in v5.
Also, auth start in the cli doesn’t do anything. It seems to just freeze and I can’t type anything else. There isn’t any error message.
1 Like
Browser logs are borked in the current release. This will have been addressed in the next alpha release. (So then we should get some useful output there at least).
If you’re having problems with the CLI that’s probably the place to debug before we get into the browser @Horace. I’m not sure how to kill running processes in windows, but would be good to attempt to shutdown all safe processes before ensuring you’re up to date with latest auth/cli (safe update, safe auth update) and trying again.
Also apologies to those waiting on a windows fix here. I did not get to this end of april. Been super focussed on at2 things the last month. Will hopefully get back to debugging here once that’s in. 
2 Likes
Both are updated to the lastest version. The cli says authd has started after authd is killed in the task manager. auth status returns an error message though, probably because authd has been killed.
[Error] AuthdClientError - Failed to establish connection with authd: [Error] ClientError - Failed to establish connection with remote QUIC endpoint: timed out
Look at the following discussion, there seems to be a problem with Win10 and the auth start command, in that discussion I proposed a workaround, give it a try: [Status: offline] SAFE Network Testnet - Vaults from home with IGD - Iteration 2 - #67 by Mindphreaker
3 Likes
Auth status works after doing this, but account creation and login doesn’t.
2 Likes
That must be because the shared testnet is down right now, you can run your own local testnet and then try to create an account: https://github.com/maidsafe/safe-api/blob/master/safe-cli/README.md#run-a-local-network
2 Likes
A new alpha release is out, that has an updated version of electron and safenodejs. So would be interesting to know if there’s any change for windows folks:
4 Likes
There doesn’t seem to be any change.
1 Like
Okay thanks for checking @Horace. I won’t get a fix for this in the next release, I’m afraid.
But I will make digging in here a prio when back at the browser proper.
1 Like