It’s important to ensure you’ve registered your IP address in order to access the SAFE Network (Alpha-2). If you haven’t already then here’s how you do that:
Download a development version of the SAFE Browser which uses a mock network to allow local development (without the need to pay PUT costs on a live SAFE Network).
Download a development version of the SAFE Browser which uses a mock network to allow local development (without the need to pay PUT costs on a live SAFE Network).
Interesting. That means the browser app (separate to the authenticator) hadn’t managed to initialise (aka was probably still trying to reach a server).
Do you have any logs @digipl ? (normally at: $TMPDIR/safe-browser.log )
[2019-04-30 12:50:18.860] [error] Error in authFromStoreResponse
[2019-04-30 12:50:18.862] [error] Unexpected (probably a logic error): Could not connect to the SAFE Network
[2019-04-30 12:50:18.863] [error] authFromStoreResponse error >>>>>>>>>>>>>
[2019-04-30 12:50:31.184] [error] Blocked URL: https://invite.maidsafe.net/
[2019-04-30 12:51:15.105] [error] Auth decision error :: undefined
[2019-04-30 12:51:26.766] [error] SAFE Fetch error: 1001 Setup Incomplete. Connection not available yet.
[2019-04-30 12:51:53.777] [error] SAFE Fetch error: 1001 Setup Incomplete. Connection not available yet.
[2019-04-30 12:53:02.279] [error] SAFE Fetch error: 1001 Setup Incomplete. Connection not available yet.
[2019-04-30 12:53:22.918] [error] SAFE Fetch error: 1001 Setup Incomplete. Connection not available yet.
[2019-04-30 12:53:28.690] [error] SAFE Fetch error: 1001 Setup Incomplete. Connection not available yet.
Analyzing the timings, I think the first four warnings 12:50:18 to 12:50:31 are before changing the IP.
I changed my IP and login without problems.
The two Fetch error are two attempts to load a page after the login.
After the two error, and surprised by the message “Setup Incomplete. Connection not available yet.” I run the Web Hosting Manager to check if the connection worked. WHM was fine.
With the WHM open, I tried three different pages and all three show the error.
I closed both, the WHM and the Browser, restarted the Browser and everything worked properly.