@happybeing I’ll need some more logs to see what’s happening in your situation.
Could you set RUST_LOG=safe=trace,qu=safe=trace and then do
safe auth stop
safe auth start
followed by
safe auth create-acc --test-coins
Once this is done could you share the contents of ~/.safe/authd/logs/safe-authd.err it will have trace logs from SCL and quic-p2p 
I’m sorry @davidpbrown, I don’t understand your question. safe-authd is a separate binary, you can start/stop/restart it using its binary directly, or for convenience using the safe CLI. The CLI still calls the safe-authd binary commands to do that, so it’s just a convenience utility that CLI provides to find the authd binary and invoke it. We get the -V functionality for free, it’s provided by the crate we use to parse the CLI commands and args, and it currently works only for the binary being executed, like the CLI binary or safe-authd binary, or safe_vault binary. Can you please rephrase your question?
$ safe *
as one.
The -V is encouraging the sense that it is one binary.
Only asked as I can’t be sure a reason someone would not have both cli and authd… and would reduce install steps.
So you mean merging the authd functionality into the safe CLI binary and having a single binary for everything? technically it’s possible, but note many users will never use the CLI and only the authd launched from SNApp, but if that’s what you mean it could be discussed/considered as it’s technically feasible.
Will we afterwards be also considering the same for the vault binary then? (not advocating just a point to make)
Still easier perhaps as
safe -V
safe_auth -V
safe-vault -V
Hi @lionel.faber - this is what I get after stopping and starting auth first:
John@John-HP MINGW64 ~/Documents/SAFEnetwork/_safe-cli
$ RUST_LOG=safe=trace,qu=safe=trace ./safe auth create-acc --test-coins
warning: invalid logging spec ‘qu=safe=trace’, ignoring it
[2020-04-15T13:29:35Z DEBUG safe] Starting SAFE CLI…
[2020-04-15T13:29:35Z DEBUG safe::cli] Processing command: CmdArgs { cmd: Some(Auth { cmd: Some(Create { config_file_str: None, sk: None, test_coins: true }) }), output_fmt: None, output_json: false, dry: false, xorurl_base: None, endpoint: None }
[2020-04-15T13:29:35Z DEBUG safe_api::api::authd_client::authd_client_api] Creating new authd client for endpoint https://localhost:33000
… then it hangs.
Oops small mistake from me there it’s:
RUST_LOG=safe=trace,qu=trace
After this is done could you follow the steps and the share the contents of ~/.safe/authd/logs/safe-authd.err
cc: @happybeing
Useful to know! The path is different but I assume that’s fine:
$ cat ~/.config/safe_vault/vault_connection_info.config
"167.71.140.27:443"
safe-authd.err hasn’t been written to for a couple of weeks so here is safe-auths.log:
INFO 2020-04-14T18:27:30.393194136+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 12662)...
INFO 2020-04-14T18:27:30.393318677+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-14T18:27:30.393853905+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
INFO 2020-04-14T18:28:45.794027811+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:28:45.794207493+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (3707466448): 'login'
INFO 2020-04-14T18:28:45.794256607+01:00 [safe-authd/requests/log_in.rs:25] Logging in to SAFE account...
INFO 2020-04-14T18:29:38.033588112+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:29:38.033745533+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (3870159741): 'status'
INFO 2020-04-14T18:29:38.033792943+01:00 [safe-authd/requests/status.rs:29] Preparing authd status report...
INFO 2020-04-14T18:30:07.039142678+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 12924)...
INFO 2020-04-14T18:30:07.039536699+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-14T18:30:07.040894035+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
INFO 2020-04-14T18:30:09.942247494+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:30:09.942437384+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (1860721091): 'status'
INFO 2020-04-14T18:30:09.942505307+01:00 [safe-authd/requests/status.rs:29] Preparing authd status report...
INFO 2020-04-14T18:30:09.942572218+01:00 [safe-authd/requests/status.rs:55] Status report sent: AuthdStatus { logged_in: false, num_auth_reqs: 0, num_notif_subs: 0, authd_version: "0.0.8" }
WARN 2020-04-14T18:30:09.943425339+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-14T18:30:09.943440204+01:00 [safe-authd/authd.rs:154] Response sent, request complete
INFO 2020-04-14T18:30:24.905856682+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:30:24.906023646+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (1288008650): 'login'
INFO 2020-04-14T18:30:24.906086490+01:00 [safe-authd/requests/log_in.rs:25] Logging in to SAFE account...
INFO 2020-04-14T18:30:34.441351082+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:30:34.441542896+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (3942603263): 'login'
INFO 2020-04-14T18:30:34.441603936+01:00 [safe-authd/requests/log_in.rs:25] Logging in to SAFE account...
ERROR 2020-04-14T18:30:56.780885918+01:00 [safe-authd/requests/log_in.rs:47] Error occurred when trying to log in: [Error] AuthError - Failed to log in: no SAFE account found with the passphrase provided
ERROR 2020-04-14T18:30:56.780984581+01:00 [safe-authd/requests/mod.rs:82] Failed processing incoming request 1288008650: [Error] AuthError - Failed to log in: no SAFE account found with the passphrase provided
INFO 2020-04-14T18:31:30.263052776+01:00 [safe-api/src/api/authenticator/auth.rs:93] Disconnected from network
INFO 2020-04-14T18:31:30.263096203+01:00 [safe-authd/requests/log_in.rs:43] Logged in successfully!
INFO 2020-04-14T18:31:30.263618863+01:00 [safe-authd/authd.rs:154] Response sent, request complete
INFO 2020-04-14T18:31:30.287430531+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:31:30.287570705+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (1507656850): 'subscribe'
INFO 2020-04-14T18:31:30.287617285+01:00 [safe-authd/requests/subscribe.rs:38] Subscribing to authorisation requests notifications...
INFO 2020-04-14T18:31:30.287664427+01:00 [safe-authd/requests/subscribe.rs:77] Subscription successful. Endpoint 'https://localhost:33002' will receive authorisation requests notifications (cert base path: "/home/mrh/.config/safe-authd-client/net.maidsafe.cli")
INFO 2020-04-14T18:31:30.288317993+01:00 [safe-authd/authd.rs:154] Response sent, request complete
WARN 2020-04-14T18:31:30.288508978+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-14T18:31:30.296221322+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:31:30.296350369+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (3905569313): 'authorise'
INFO 2020-04-14T18:31:30.296405629+01:00 [safe-authd/requests/authorise.rs:56] Authorising application...
INFO 2020-04-14T18:31:30.296629495+01:00 [safe-authd/requests/authorise.rs:64] The following application authorisation request (2244060075) was received:
INFO 2020-04-14T18:31:30.296696182+01:00 [safe-authd/requests/authorise.rs:68] AuthReq { app: AppExchangeInfo { id: "net.maidsafe.cli", scope: None, name: "SAFE CLI", vendor: "MaidSafe.net Ltd" }, app_container: false, app_permissions: AppPermissions { transfer_coins: true, perform_mutations: true, get_balance: true }, containers: {} }
INFO 2020-04-14T18:31:31.139452845+01:00 [safe-authd/notifs.rs:141] Notifying subscriber: https://localhost:33002
INFO 2020-04-14T18:31:31.145434701+01:00 [safe-authd/notifs.rs:159] Subscriber's response: Auth req notification from app id 'net.maidsafe.cli' sent to user
INFO 2020-04-14T18:31:31.145523026+01:00 [safe-authd/notifs.rs:104] Decision obtained for auth req id: 2244060075 - from app id: net.maidsafe.cli: None
INFO 2020-04-14T18:31:31.152377918+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:31:31.152527811+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (2924826254): 'allow'
INFO 2020-04-14T18:31:31.152589490+01:00 [safe-authd/requests/allow.rs:19] Allowing authorisation request...
INFO 2020-04-14T18:31:31.152647533+01:00 [safe-authd/requests/allow.rs:33] Authorisation request (2244060075) allowed successfully
INFO 2020-04-14T18:31:31.152819582+01:00 [safe-authd/requests/authorise.rs:161] Let's request the authenticator lib to authorise the request '2244060075'...
INFO 2020-04-14T18:31:31.153279164+01:00 [safe-authd/authd.rs:154] Response sent, request complete
INFO 2020-04-14T18:31:31.153393505+01:00 [safe-api/src/api/authenticator/auth.rs:312] Request was recognised as a general app auth request
WARN 2020-04-14T18:31:31.153524628+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-14T18:31:32.366050568+01:00 [safe-authd/requests/authorise.rs:168] Authorisation request (2244060075) was allowed and response sent back to the application
WARN 2020-04-14T18:31:32.366489203+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-14T18:31:32.366506764+01:00 [safe-authd/authd.rs:154] Response sent, request complete
INFO 2020-04-14T18:31:32.387169867+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T18:31:32.387232631+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (2845634995): 'unsubscribe'
INFO 2020-04-14T18:31:32.387279855+01:00 [safe-authd/requests/unsubscribe.rs:19] Unsubscribing from authorisation requests notifications...
INFO 2020-04-14T18:31:32.387293556+01:00 [safe-authd/requests/unsubscribe.rs:27] Unsubscription successful. Endpoint 'https://localhost:33002' will no longer receive authorisation requests notifications
INFO 2020-04-14T18:31:32.387502182+01:00 [safe-authd/authd.rs:154] Response sent, request complete
WARN 2020-04-14T18:31:32.387582461+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
ERROR 2020-04-14T18:32:56.782303846+01:00 [safe-authd/authd.rs:121] [Error] GeneralError - Failed to shutdown stream: [Error] GeneralError - Failed to shutdown the response stream gracefully: connection closed: timed out
WARN 2020-04-14T18:32:56.782314984+01:00 [jsonrpc-quic/server_endpoint.rs:149] Failed to read incoming request: timed out
WARN 2020-04-14T18:33:30.264738014+01:00 [jsonrpc-quic/server_endpoint.rs:149] Failed to read incoming request: timed out
INFO 2020-04-14T19:01:43.382720737+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-14T19:01:43.382887236+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (4112294694): 'status'
INFO 2020-04-14T19:01:43.382927826+01:00 [safe-authd/requests/status.rs:29] Preparing authd status report...
INFO 2020-04-14T19:01:43.382965412+01:00 [safe-authd/requests/status.rs:55] Status report sent: AuthdStatus { logged_in: true, num_auth_reqs: 0, num_notif_subs: 0, authd_version: "0.0.8" }
INFO 2020-04-14T19:01:43.383448494+01:00 [safe-authd/authd.rs:154] Response sent, request complete
WARN 2020-04-14T19:01:43.383547268+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T11:55:14.841397852+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 21986)...
INFO 2020-04-15T11:55:14.841524265+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T11:55:14.842112298+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
INFO 2020-04-15T11:57:37.614996104+01:00 [jsonrpc-quic/server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T11:57:37.615138597+01:00 [safe-authd/requests/mod.rs:39] Processing new incoming request (1934776970): 'login'
INFO 2020-04-15T11:57:37.615178090+01:00 [safe-authd/requests/log_in.rs:25] Logging in to SAFE account...
ERROR 2020-04-15T11:59:07.798942864+01:00 [safe-authd/requests/log_in.rs:47] Error occurred when trying to log in: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
ERROR 2020-04-15T11:59:07.798999094+01:00 [safe-authd/requests/mod.rs:82] Failed processing incoming request 1934776970: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
WARN 2020-04-15T11:59:07.799357414+01:00 [jsonrpc-quic/server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T11:59:07.799429931+01:00 [safe-authd/authd.rs:154] Response sent, request complete
INFO 2020-04-15T14:28:04.593655977+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 3738)...
INFO 2020-04-15T14:28:04.594067662+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T14:28:04.595530018+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
INFO 2020-04-15T14:31:45.147867169+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 3932)...
DEBUG 2020-04-15T14:31:45.147995399+01:00 [safe-authd/operations.rs:149] PID file to be written at: "/home/mrh/.safe/authd/logs/safe-authd.pid"
INFO 2020-04-15T14:31:45.148367798+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T14:31:45.149878122+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
INFO 2020-04-15T14:40:38.522344482+01:00 [safe-authd/operations.rs:146] authd instance starting (PID: 4499)...
DEBUG 2020-04-15T14:40:38.522470023+01:00 [safe-authd/operations.rs:149] PID file to be written at: "/home/mrh/.safe/authd/logs/safe-authd.pid"
INFO 2020-04-15T14:40:38.522741380+01:00 [safe-authd/operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T14:40:38.523826020+01:00 [safe-authd/authd.rs:80] Listening on 127.0.0.1:33000
Thanks!
And could you set it when you run safe auth start as well so the auth daemon will pick up these logs levels too
I have wondered occasionally as to why they ere not all rolled up into one command. The GUI argument for Joe User does have some weight to it, however.
What would be the file size/ memory cost of aggregating them into one command?
That’s already the case, but you need to use the corresponding binary.
I’m not sure but that’s definitely something against this proposal, if you have cli and authd in same binary, when you launch it as a daemon it will be a copy of the whole cli process in memory AFAIK, currently we have CLI binary ~26MB and authd binary ~20MB, not sure what would be the total size when merged together, for sure not ~46MB as they have many dependencies in common, so it’ll be less than that.
INFO 2020-04-15T08:06:38.092963600+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 14920)...
INFO 2020-04-15T08:06:38.093960700+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T08:06:38.120911200+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
INFO 2020-04-15T08:07:52.609922500+01:00 [jsonrpc-quic\server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T08:07:52.610421+01:00 [safe-authd\requests\mod.rs:39] Processing new incoming request (3364517591): 'login'
INFO 2020-04-15T08:07:52.610421+01:00 [safe-authd\requests\log_in.rs:25] Logging in to SAFE account...
INFO 2020-04-15T08:08:22.629124700+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
INFO 2020-04-15T08:08:52.681238900+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
INFO 2020-04-15T08:09:22.732867100+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
ERROR 2020-04-15T08:09:22.781776400+01:00 [safe-authd\requests\log_in.rs:47] Error occurred when trying to log in: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
ERROR 2020-04-15T08:09:22.781776400+01:00 [safe-authd\requests\mod.rs:82] Failed processing incoming request 3364517591: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
INFO 2020-04-15T08:09:22.782274200+01:00 [safe-authd\authd.rs:154] Response sent, request complete
WARN 2020-04-15T08:09:22.782773200+01:00 [jsonrpc-quic\server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T08:16:20.994738400+01:00 [jsonrpc-quic\server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T08:16:20.994738400+01:00 [safe-authd\requests\mod.rs:39] Processing new incoming request (2843568257): 'login'
INFO 2020-04-15T08:16:20.994738400+01:00 [safe-authd\requests\log_in.rs:25] Logging in to SAFE account...
INFO 2020-04-15T08:31:32.966724+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 9656)...
INFO 2020-04-15T08:31:32.967223200+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T08:31:32.981184700+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
INFO 2020-04-15T08:34:32.927129700+01:00 [jsonrpc-quic\server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T08:34:32.927629700+01:00 [safe-authd\requests\mod.rs:39] Processing new incoming request (2819395728): 'status'
INFO 2020-04-15T08:34:32.927629700+01:00 [safe-authd\requests\status.rs:29] Preparing authd status report...
INFO 2020-04-15T08:34:32.927629700+01:00 [safe-authd\requests\status.rs:55] Status report sent: AuthdStatus { logged_in: false, num_auth_reqs: 0, num_notif_subs: 0, authd_version: "0.0.8" }
INFO 2020-04-15T08:34:32.928129200+01:00 [safe-authd\authd.rs:154] Response sent, request complete
WARN 2020-04-15T08:34:32.928129200+01:00 [jsonrpc-quic\server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T08:39:17.121759200+01:00 [jsonrpc-quic\server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T08:39:17.121759200+01:00 [safe-authd\requests\mod.rs:39] Processing new incoming request (3659181940): 'status'
INFO 2020-04-15T08:39:17.121759200+01:00 [safe-authd\requests\status.rs:29] Preparing authd status report...
INFO 2020-04-15T08:39:17.121759200+01:00 [safe-authd\requests\status.rs:55] Status report sent: AuthdStatus { logged_in: false, num_auth_reqs: 0, num_notif_subs: 0, authd_version: "0.0.8" }
INFO 2020-04-15T08:39:17.122258600+01:00 [safe-authd\authd.rs:154] Response sent, request complete
WARN 2020-04-15T08:39:17.122258600+01:00 [jsonrpc-quic\server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T08:39:30.075675400+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 3004)...
ERROR 2020-04-15T08:39:30.076174400+01:00 [safe-authd\main.rs:97] safe-authd error: [Error] AuthdAlreadyStarted - Failed to start safe-authd daemon (C:\Users\John\.safe\authd\safe-authd.exe)
INFO 2020-04-15T08:39:45.409166900+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 9804)...
INFO 2020-04-15T08:39:45.409665900+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T08:39:45.423639800+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
INFO 2020-04-15T08:40:01.623022300+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 2196)...
INFO 2020-04-15T08:40:01.623521700+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T08:40:01.638493800+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
INFO 2020-04-15T08:40:25.777117300+01:00 [jsonrpc-quic\server_endpoint.rs:160] Got new request's bytes
INFO 2020-04-15T08:40:25.777614500+01:00 [safe-authd\requests\mod.rs:39] Processing new incoming request (3815158861): 'login'
INFO 2020-04-15T08:40:25.777614500+01:00 [safe-authd\requests\log_in.rs:25] Logging in to SAFE account...
INFO 2020-04-15T08:40:55.793309400+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
INFO 2020-04-15T08:41:25.845436900+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
INFO 2020-04-15T08:41:55.897065100+01:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\quic-p2p-0.5.0\src\connect.rs:253] Peer 167.71.140.27:443 has a connection to us but we couldn't connect to it. All connections to this peer will now be severed.
ERROR 2020-04-15T08:41:55.945475100+01:00 [safe-authd\requests\log_in.rs:47] Error occurred when trying to log in: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
ERROR 2020-04-15T08:41:55.945475100+01:00 [safe-authd\requests\mod.rs:82] Failed processing incoming request 3815158861: [Error] AuthError - Failed to log in: Core error: Unexpected: Connection timed out when bootstrapping to the network
WARN 2020-04-15T08:41:55.945974700+01:00 [jsonrpc-quic\server_endpoint.rs:145] Connection terminated
INFO 2020-04-15T08:41:55.945974700+01:00 [safe-authd\authd.rs:154] Response sent, request complete
INFO 2020-04-15T14:26:35.641203200+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 9696)...
DEBUG 2020-04-15T14:26:35.641203200+01:00 [safe-authd\operations.rs:149] PID file to be written at: "C:\\Users\\John\\.safe\\authd\\logs\\safe-authd.pid"
DEBUG 2020-04-15T14:26:35.641701300+01:00 [safe-authd\operations.rs:185] Failed to lock PID file with OS error code: 33
ERROR 2020-04-15T14:26:35.645693600+01:00 [safe-authd\main.rs:97] safe-authd error: [Error] AuthdAlreadyStarted - Failed to start safe-authd daemon (C:\Users\John\.safe\authd\safe-authd.exe)
INFO 2020-04-15T14:26:58.554104800+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 3216)...
DEBUG 2020-04-15T14:26:58.554602100+01:00 [safe-authd\operations.rs:149] PID file to be written at: "C:\\Users\\John\\.safe\\authd\\logs\\safe-authd.pid"
INFO 2020-04-15T14:26:58.555101400+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T14:26:58.572568500+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
INFO 2020-04-15T14:29:18.312265700+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 12000)...
DEBUG 2020-04-15T14:29:18.312265700+01:00 [safe-authd\operations.rs:149] PID file to be written at: "C:\\Users\\John\\.safe\\authd\\logs\\safe-authd.pid"
DEBUG 2020-04-15T14:29:18.312765100+01:00 [safe-authd\operations.rs:185] Failed to lock PID file with OS error code: 33
ERROR 2020-04-15T14:29:18.312765100+01:00 [safe-authd\main.rs:97] safe-authd error: [Error] AuthdAlreadyStarted - Failed to start safe-authd daemon (C:\Users\John\.safe\authd\safe-authd.exe)
INFO 2020-04-15T14:31:36.034215+01:00 [safe-authd\operations.rs:146] authd instance starting (PID: 12508)...
DEBUG 2020-04-15T14:31:36.034215+01:00 [safe-authd\operations.rs:149] PID file to be written at: "C:\\Users\\John\\.safe\\authd\\logs\\safe-authd.pid"
INFO 2020-04-15T14:31:36.035213200+01:00 [safe-authd\operations.rs:174] Initialising SAFE Authenticator services...
INFO 2020-04-15T14:31:36.049686300+01:00 [safe-authd\authd.rs:80] Listening on [::1]:33000
It seems I’m losing track of things now 
@happybeing @JPL I’ll be DM-ing the both of you separately and we’ll take it from there. I hope that’s okay
Have you got a previous instance hanging?..
try
ps aux | grep 'safe'
or ye olde method: Turn it off and back on again?
always my first point of call 
reinstalled too.
$ ps aux | grep ‘safe’
josh 2462 0.0 0.0 14424 1032 pts/0 S+ 09:04 0:00 grep --color=auto safe
status give me this, $ safe auth status
Sending request to authd to obtain a status report…
[2020-05-29T13:00:54Z ERROR safe] safe-cli error: [Error] AuthdClientError - Failed to establish connection with authd: [Error] ClientError - Failed to establish connection with remote QUIC endpoint: timed out
I need to make it clear that using the command line is rocky ground for me! (doing a online course at the mo so that I can move on from utter frustration)
Hand holding available if you want to install AnyDesk
DM me for details - but it wont be untill tomorrow - BBQ and beer is incoming
thank you, I have a little more stumble around in the dark left in me… if I don’t figure it out shortly though I will definitely take up that offer!
OK you are welcome. meantime try…
safe networks
IF you see “shared section” blah in the output then
safe networks switch shared-section
I have made some progress, seems that I messed up something with the install. After educating myself on installing scripts… I’m in and feeling like I have summited Everest 
Walking away while I’m impressed with myself for a while. 
