So after getting level 1 on the forum, I have downloaded and unzipped the SAFE browser, safe-browser-v0.12.0-linux-x64
on Linux Mint 19.1 XFCE edition.
Browser runs beautifully. After getting my invite and inputting it into account creation, it accepted my secret and password (what’s the diff?) before hanging for several minutes. Finally, this error came up.
Account containers creation error: NFS error: NfsError::CoreError -> Request has timed out - CoreError::RequestTimeout. Login to attempt recovery.
This error is in small red text underneath the invite token on the second page of the SAFE Authenticator page.
Any suggestions? Could it be blocked by my ISP?
Quick question… are you running from the same IP as the one you registered at the time of invite?
If you have changed you just need to whip back on to the invite page and update the IP to the current one.
I’ve tried to reproduce your issue but it works OK for me - if you don’t set the IP address at the invite page there is an error when attempting to log in with the browser but it is not the one you have specified.
Just to confirm, these are the steps you need to go through:
I have a similar issue with my home connection using the ISP router, I’m not sure if I’ve ever got the timeout error exactly, but it does take a loooong time to log in or in general for any operation I do interacting with the alpha2 network. I usually have to switch to use my mobile as hotspot to be able to connect and operate normally. So there seems to be some problem with some routers, or ISP’s setup perhaps
I also have this problem sometimes - but only with Linux not with Windows. I have other problems with Windows re the Web Hosting Manager not connecting (which @bochaco@hunterlester and I tried to get to the bottom of a while back) but only on one machine. So it looks like one (or more than one) of those strange bugs that only affect a few people. Hopefully it will fix itself as the codebase matures. @jorxster Do you have another machine you could try, or another OS?
(For clarity I don’t mean you need to have authorised these for the browser to navigate to sites - you can do so without signing in - but this would confirm whether or not you have successfully connected to the SAFE network.)
That was actually part of the solution!
Because of a big orange header warning, I never saw a prompt that SAFE Browser was asking for permission.
I have authorised it, and it is working , on my home network! Sites load in a timely manner.