Couldn't connect to the Safe Network

[keemaa]

Hello Safers
I installed Safe Launcher and allowed its connections through firewall, but I get this message when I try to connect "Couldn't connect to the Safe Network".

Any help will be appreciated.
Thanks in advance.

[ethanpailes]

I think that is because there is no test net running right now. You can still build the project against mock_routing and run a local version if you want to play with the API.

[porteron]

Having same issue.

[alepacheco]

Same here

[frabrunelle]

There is no testnet running right now, so it's normal to see this error.

Developers can use "mock routing" (a simulated version of the network) to build apps 🙂

For the current SAFE API, you can follow the instructions in the README of SAFE Launcher to build it using mock routing.

[gubi]

This is my terminal output:

:~$ safe_launcher
/opt/maidsafe/safe_launcher/safe_launcher

DEBUG 00:47:58.695 - Starting FFI worker client
DEBUG 00:47:58.707 - Sending message to FFI - bdcd718e-6ce1-427d-ba62-0a2ae20e06b6 - get-log-path - 
DEBUG 00:47:58.731 - Application starting
TRACE 22:47:58.860616219 [safe_core::ffi mod.rs:415] FFI Dropping vector.
DEBUG 00:47:58.922 - Sending FFI initialisation request
DEBUG 00:47:58.923 - Sending message to FFI - 5fbb8bc2-2f25-48f2-9e71-48615b7fd805 - connect - 
DEBUG 00:47:58.924 - FFI response code 0 for id - logFilePath
TRACE 22:47:58.924762677 [safe_core::ffi mod.rs:181] FFI create unregistered client.
TRACE 22:47:58.924796261 [safe_core::core::client mod.rs:78] Creating unregistered client.
DEBUG 00:47:58.973 - FFI/mod/auth.js - Create Unregistered Client Handle
TRACE 22:47:59.232302323 [safe_core::core::client mod.rs:87] Waiting to get connected to the Network...
DEBUG 22:48:09.326849453 [routing::core core.rs:1080] Disconnected(bc3312..) Failed to bootstrap.
TRACE 22:48:09.326926557 [safe_core::core::client::message_queue message_queue.rs:172] EventReceiverThread received: Event::Terminate
INFO 22:48:09.326948995 [safe_core::core::client::message_queue message_queue.rs:193] Received a Terminate event. Informing 1 observers.
WARN 22:48:09.326968874 [safe_core::core::client mod.rs:91] Could not connect to the Network. Unexpected: Disconnected
INFO 22:48:09.327740179 [safe_core::ffi mod.rs:182] 
FFI cross-boundary error propagation:
 --------------------------------------------------
| **ERRNO: -15** Operation aborted - CoreError::OperationAborted
 --------------------------------------------------


DEBUG 00:48:09.328 - Network state change event received :: 1 :: false
INFO 00:48:09.329 - Network connection lost

[frabrunelle]

@gubi: The SAFE Network Alpha 1 network has been offline since March 14 (see this post), so it's normal to see this error.

See the weekly dev updates for more info on what we're working on: https://safenetforum.org/c/development/updates

[gubi]

Wait.
I was in version 0.8.0, installed via apt.
Now I switched to 0.11.0 manually (dowloaded files from here and moved to /opt/maidsafe/safe-launcher dir) and the result is:

:~$ safe-launcher 

info: Server started
debug: Add event listener - error
debug: Add event listener - started
debug: Add event listener - stopped
debug: Add event listener - sesssion_created
debug: Add event listener - session_creation_failed
debug: Add event listener - session_removed
debug: Add event listener - data_uploaded
debug: Add event listener - data_downloaded
debug: Add event listener - activity_new
debug: Add event listener - activity_update
debug: Add event listener - auth_request
debug: Add event listener - invite_token
info: API server started
I 17-05-07 23:23:35.320003 Bootstrapping(ceef6d..) Failed to bootstrap. Terminating.
I 17-05-07 23:23:35.320116 Received a Terminate event. Informing 1 observers.
W 17-05-07 23:23:35.320156 Could not connect to the Network. Unexpected: Disconnected
I 17-05-07 23:23:35.320574 
FFI cross-boundary error propagation:
 --------------------------------------------------
| **ERRNO: -15** FfiError::CoreError -> Operation aborted - CoreError::OperationAborted
 --------------------------------------------------


error: FFI :: Auth :: Get unregistered session :: -15

Any suggestions?

[frabrunelle]

SAFE Launcher version 0.8.0 was for the Alpha 1 network. And SAFE Launcher v0.11.0 was for the Test 16 network.

Test 16 has been offline since April 19 (see this post), so it's normal to see this error.

[gubi]

Ok, great.
A normal way to discover the software? 😄

[frabrunelle]

If you'd like to try SAFE Launcher, you can follow the instructions in the README to build it using the mock network (a simulation of the network): https://github.com/maidsafe/safe_launcher#installation 🙂

You could also try to build the SAFE Authenticator (which is going to replace SAFE Launcher in the next testnet) as we explained in the last dev update: https://safenetforum.org/t/maidsafe-dev-update-may-4-2017/13527

I would also recommend reading this blog post for more info: https://blog.maidsafe.net/2017/05/04/safe-network-development-summary-may-2017/

The patience app developers have shown to this point is soon to be rewarded. The process of converting our APIs away from a REST paradigm to SDKs was essential to cater for mobile devices, as the requirement for REST APIs to maintain state would not have worked with mobile devices that disconnect and reconnect regularly. Users of the SAFE Network will gain access through the Authenticator, a secure gateway that protects user credentials from the application itself. The Authenticator is currently being bundled with the SAFE browser and will enable users to securely authenticate themselves onto the network, or enable them to browse publicly available data without logging in.

[gubi]

Ok, cool many thanks 🙂

[hakunin]

Too bad the testnet isn't running all the time. Would have been cool to see it working.