Routing client error -> Account does not exist for client


#1

This is my first attempt at doing some development with safenet, things seemed to go well to start with, but
I have some issues with authentication. It seems to be randomly logging me out and my accounts vanishes for no reason as well (I have to sign up again when it happens). My main issue is getting the app in the tutorial to work consistently when I refresh.

From console:

Error: Routing client error -> Account does not exist for client

Versions:

  • node 9.7.1
  • npm 6.0.0
  • windows 10 pro
  • Peruse-v0.7.0-win-x64-dev
  • safe_vault-v0.17.2-win-x64

What I did:

I followed this guide:
https://hub.safedev.org/platform/web/

I cloned the examples and my safenetwork.js now looks like this:
https://pastebin.com/NmWS6sPp

Step by step:

  1. Started vault:
    safe_vault.exe --first
    output:
    Running safe_vault v0.17.2
    ==========================
    I 18-10-16 21:24:55.588375 Node(4e71f7…()) Started a new network as a seed node.
    I 18-10-16 21:24:55.588876 Created chunk store at C:\Users\Warz\AppData\Local\Temp\safe_vault_chunk_store.EXa8N1eFPg8g with capacity of 2147483648 bytes.

  2. npm start
    output:
    safe_web_app_quick_start@1.0.0 start O:\wamp\www\maidsafe\safe_examples\safe_web_app_quick_start
    neutrino start

  3. Started Peruse-v0.7.0-win-x64-dev\Peruse.exe

  4. Tried to sign in with account secret and account password
    output: Account does not exist
    This seems to happen a lot.
    So I go to create account and go through the whole procedure to sign up again


  1. Peruse Browser requests Auth Permission ACCEPT DENY:
    I accept, the Peruse Browser icon appears under authorized apps
    account status 9/1000

  1. I open a new tab in peruse browser and go to localhost:5000

  1. Warz Test webapp requests Auth Permission ACCEPT DENY:
    I accept

  1. The script seems to work fine. The mutable entries appear, see: i.imgur DOT com/PMCKJX1.png

  1. I refresh and get the “Warz Test webapp requests Auth Permission ACCEPT DENY:” message again,
    which I accept.
  2. This time it does not work. The developer console log shows this error:

{message: “Core error: Routing client error -> Account does not exist for client”, stack: “-101: Core error: Routing client error -> Account …s\app.asar\node_modules\ffi\lib\callback.js:66:25”}message: "Core error: Routing client error -> Account does not exist for client"stack: "-101: Core error: Routing client error -> Account does not exist for client↵ at module.exports (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:32:10)↵ at args.push.ffi.Callback.restArgs (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_base.js:105:27)↵ at Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules\ffi\lib\callback.js:66:25"proto: Error
at makeError (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:23:17)
at module.exports (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:31:13)
at args.push.ffi.Callback.restArgs (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_base.js:105:27)
at Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules\ffi\lib\callback.js:66:25
Promise rejected (async)
(anonymous) @ App.vue:40
Promise resolved (async)
(anonymous) @ App.vue:39
created @ App.vue:38
callHook @ vue.runtime.esm.js:2917
Vue._init @ vue.runtime.esm.js:4626
VueComponent @ vue.runtime.esm.js:4794
createComponentInstanceForVnode @ vue.runtime.esm.js:4306
init @ vue.runtime.esm.js:4127
createComponent @ vue.runtime.esm.js:5604
createElm @ vue.runtime.esm.js:5551
patch @ vue.runtime.esm.js:6126
Vue._update @ vue.runtime.esm.js:2656
updateComponent @ vue.runtime.esm.js:2784
get @ vue.runtime.esm.js:3138
Watcher @ vue.runtime.esm.js:3127
mountComponent @ vue.runtime.esm.js:2791
./node_modules/vue/dist/vue.runtime.esm.js.Vue.$mount @ vue.runtime.esm.js:7995
Vue._init @ vue.runtime.esm.js:4636
Vue @ vue.runtime.esm.js:4725
./src/index.js @ index.js:4
webpack_require @ bootstrap 31e00c9e07c4e93564e2:678
fn @ bootstrap 31e00c9e07c4e93564e2:88
0 @ safenetwork.js:60
webpack_require @ bootstrap 31e00c9e07c4e93564e2:678
./node_modules/ansi-html/index.js.module.exports @ bootstrap 31e00c9e07c4e93564e2:724
(anonymous) @ index.js:728

Screenshot: i.imgur DOT com/fxUXEzn.png

  1. I navigate back to the other tab and refresh, I end up at
    safe-auth://home/#/login and it’s asking me to sign in.

  2. I sign in, and it now looks like this: i.imgur DOT com/gVgnjR5.png (I notice account status is now 16/1000 instead of 9/1000).

  3. I navigate back to the tab with localhost:5000 and refresh

  4. I accept once again and get the same error as before (routing client error)

  5. I go back to the other tab (safe-auth://home) and refresh. I am still logged in…

Ideas?


#2

Hi @warz,

Thank you for the post.
Looks like this may be the same or related to the problem in this thread.

It looks like step 1 may be redundant, because Peruse-v0.7.0-win-x64-dev\Peruse.exe CRUD’s against a MockVault file that is created in your temp_dir.
But that’s great that you’re experimenting with running your own local network.

Devs seems to be observing a corrupted MockVault more often now, so we’re pushing up the task in priority to understand why.

Have you tried connecting a non-dev SAFE Browser release to your local test network?


#3

How do I do this? I tried launching the non-dev Peruse browser while running safe vault, it only resulted in “Core error: Unexpected: Could not connect to the SAFE Network”. I was not able to sign up / login.


#4

Following this tutorial:

You should run at least min_section_size instances of the vault binary before trying to connect any clients

Then in your browser directory, where the executable resides, replace peruse.crust.config with the contents of safe_vault.crust.config that you created to run your local vaults.
Exception for OSX users: Use this example to observe where the crust.config file should reside.
NOTE: at the time of writing the latest release for download is still named Peruse. Subsequent versions will be named SAFE Browser, so you’d then be replacing safe-browser.crust.config, not peruse.curst.config.

Now execute your browser and it should connect to your local test net.


For those whom are building SAFE Browser yourselves and want to use yarn prod-dev instead of packaging it:

  • Replace the contents of the crust.config file with the contents of the safe_vault.crust.config file that you created to run your local vaults.
  • Run one of these three commands based on your platform
  • yarn prod-dev, assuming you’ve already yarn, yarn rebuild, yarn build, see README.

As always, let me know your issues so we can get you sorted.


Error using Peruse dev browser v0.6.0
Error using Peruse dev browser v0.6.0
#5

@hunterlester Thank you. I was able to connect to my vaults and use the non-dev Peruse browser now. The script worked fine on first try, and I was able to refresh with no issues multiple times (I think I tried 4-5 refreshes).

However, after typing this message, I went back and refreshed once more, this time it did not ask for authentication. I went to the tab safe-auth://home and now I am on the login page, so apparently I was logged out there. Trying to login I get this:

Core error: Unexpected: Could not connect to the SAFE Network

I was running 6 instances of safe vault, the first started with --first

I tried adding 1 more safe vault after the connection error, to no avail.

For the record: min_section_size = 5.

This is the console log for the first safe vault instance:

Z:\executable\safe_vault-v0.17.2-win-x64>safe_vault.exe --first
I 18-10-17 21:32:52.771815

Running safe_vault v0.17.2
==========================
I 18-10-17 21:32:55.286501 Node(33d9fd..()) Started a new network as a seed node.
I 18-10-17 21:32:55.304048 Created chunk store at C:\Users\Warz\AppData\Local\Temp\safe_vault_chunk_store.D13UxeehgMBv with capacity of 2147483648 bytes.
I 18-10-17 21:34:06.128878 Node(33d9fd..()) Expecting candidate with old name 17a1f6...
I 18-10-17 21:34:06.129880 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name 17a1f6...
I 18-10-17 21:34:11.248991 Node(33d9fd..()) Sending resource proof challenge to candidate 17a1f6..->857de4..
I 18-10-17 21:34:11.277066 Node(33d9fd..()) Candidate 857de4.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:34:11.303136 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate 857de4...
I 18-10-17 21:34:11.303637 Node(33d9fd..()) Our section with Prefix() has approved candidate 857de4...
I 18-10-17 21:34:11.306144 Node(33d9fd..()) Added 857de4.. to routing table.
I 18-10-17 21:34:11.306144  --------------------------------------------
I 18-10-17 21:34:11.306144 | Node(33d9fd..()) - Routing Table size:   1 |
I 18-10-17 21:34:11.306144 | Exact network size: 2                      |
I 18-10-17 21:34:11.306144  --------------------------------------------
I 18-10-17 21:34:15.919410 Node(33d9fd..()) Expecting candidate with old name 3e9451...
I 18-10-17 21:34:15.921917 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name 3e9451...
I 18-10-17 21:34:20.957807 Node(33d9fd..()) Sending resource proof challenge to candidate 3e9451..->b48931..
I 18-10-17 21:34:20.982873 Node(33d9fd..()) Candidate b48931.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:34:20.982873 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate b48931...
I 18-10-17 21:34:20.999417 Node(33d9fd..()) Our section with Prefix() has approved candidate b48931...
I 18-10-17 21:34:20.999919 Node(33d9fd..()) Added b48931.. to routing table.
I 18-10-17 21:34:20.999919  --------------------------------------------
I 18-10-17 21:34:20.999919 | Node(33d9fd..()) - Routing Table size:   2 |
I 18-10-17 21:34:20.999919 | Exact network size: 3                      |
I 18-10-17 21:34:20.999919  --------------------------------------------
I 18-10-17 21:34:21.783502 Node(33d9fd..()) Expecting candidate with old name 40699f...
I 18-10-17 21:34:21.786009 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name 40699f...
I 18-10-17 21:34:26.836439 Node(33d9fd..()) Sending resource proof challenge to candidate 40699f..->5e9d57..
I 18-10-17 21:34:26.837942 Node(33d9fd..()) Candidate 5e9d57.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:34:26.838444 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate 5e9d57...
I 18-10-17 21:34:26.847968 Node(33d9fd..()) Our section with Prefix() has approved candidate 5e9d57...
I 18-10-17 21:34:26.848470 Node(33d9fd..()) Added 5e9d57.. to routing table.
I 18-10-17 21:34:26.848971  --------------------------------------------
I 18-10-17 21:34:26.848971 | Node(33d9fd..()) - Routing Table size:   3 |
I 18-10-17 21:34:26.848971 | Exact network size: 4                      |
I 18-10-17 21:34:26.848971  --------------------------------------------
I 18-10-17 21:34:49.322736 Node(33d9fd..()) Expecting candidate with old name e316f4...
I 18-10-17 21:34:49.325743 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name e316f4...
I 18-10-17 21:34:54.381186 Node(33d9fd..()) Sending resource proof challenge to candidate e316f4..->d944c9..
I 18-10-17 21:34:54.383191 Node(33d9fd..()) Candidate d944c9.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:34:54.383191 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate d944c9...
I 18-10-17 21:34:54.404248 Node(33d9fd..()) Our section with Prefix() has approved candidate d944c9...
I 18-10-17 21:34:54.404248 Node(33d9fd..()) Added d944c9.. to routing table.
I 18-10-17 21:34:54.405250  --------------------------------------------
I 18-10-17 21:34:54.405250 | Node(33d9fd..()) - Routing Table size:   4 |
I 18-10-17 21:34:54.405250 | Exact network size: 5                      |
I 18-10-17 21:34:54.405250  --------------------------------------------
I 18-10-17 21:37:39.441120 Node(33d9fd..()) - Connected clients: 1, cumulative: 1
I 18-10-17 21:38:18.368625 Node(33d9fd..()) - Connected clients: 2, cumulative: 2
I 18-10-17 21:38:18.526044 This vault has received 1 Client Get requests. Chunks stored: Immutable: 0, Mutable: 0. Total stored: 0 bytes.
I 18-10-17 21:38:18.601244 Node(33d9fd..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048576
I 18-10-17 21:38:18.601244 Node(33d9fd..()) - Connected clients: 1, cumulative: 2
I 18-10-17 21:38:45.410032 Node(33d9fd..()) - Connected clients: 2, cumulative: 3
I 18-10-17 21:38:45.484229 Managing 1 client accounts.
I 18-10-17 21:38:52.024122 Node(33d9fd..()) - Connected clients: 3, cumulative: 4
I 18-10-17 21:39:17.945560 Node(33d9fd..()) - Connected clients: 4, cumulative: 5
I 18-10-17 21:39:27.040242 Node(33d9fd..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048997
I 18-10-17 21:39:27.040242 Node(33d9fd..()) - Connected clients: 3, cumulative: 5
I 18-10-17 21:39:32.905338 Node(33d9fd..()) - Connected clients: 4, cumulative: 6
I 18-10-17 21:39:35.461133 Node(33d9fd..()) Stats - Client total session traffic from V4(192.168.208.1) - 1048997
I 18-10-17 21:39:35.461133 Node(33d9fd..()) - Connected clients: 3, cumulative: 6
I 18-10-17 21:39:39.888907 Node(33d9fd..()) - Connected clients: 4, cumulative: 7
I 18-10-17 21:39:43.610301 Node(33d9fd..()) Stats - Client total session traffic from V4(192.168.47.1) - 1048997
I 18-10-17 21:39:43.610301 Node(33d9fd..()) - Connected clients: 3, cumulative: 7
I 18-10-17 21:39:47.725242 Node(33d9fd..()) - Connected clients: 4, cumulative: 8
I 18-10-17 21:40:15.965847 Node(33d9fd..()) Expecting candidate with old name d73318...
I 18-10-17 21:40:15.968855 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name d73318...
I 18-10-17 21:40:21.014270 Node(33d9fd..()) Sending resource proof challenge to candidate d73318..->1705d6..
I 18-10-17 21:40:21.018280 Node(33d9fd..()) Candidate 1705d6.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:40:21.018280 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate 1705d6...
I 18-10-17 21:40:21.037332 Node(33d9fd..()) Our section with Prefix() has approved candidate 1705d6...
I 18-10-17 21:40:21.037833 Node(33d9fd..()) Added 1705d6.. to routing table.
I 18-10-17 21:40:21.038334  --------------------------------------------
I 18-10-17 21:40:21.038334 | Node(33d9fd..()) - Routing Table size:   5 |
I 18-10-17 21:40:21.038334 | Exact network size: 6                      |
I 18-10-17 21:40:21.038334  --------------------------------------------
I 18-10-17 21:40:21.053374 This vault has received 52 Client Get requests. Chunks stored: Immutable: 0, Mutable: 13. Total stored: 5339 bytes.
I 18-10-17 21:43:04.521070 Node(33d9fd..()) Stats - Client total session traffic from V4(127.0.0.1) - 1048997
I 18-10-17 21:43:04.521070 Node(33d9fd..()) - Connected clients: 3, cumulative: 8
I 18-10-17 21:43:05.416451 This vault has received 53 Client Get requests. Chunks stored: Immutable: 0, Mutable: 13. Total stored: 5339 bytes.
I 18-10-17 21:43:35.274341 Node(33d9fd..()) - Connected clients: 4, cumulative: 9
I 18-10-17 21:43:35.281360 Node(33d9fd..()) Stats - Client total session traffic from V4(127.0.0.1) - 1048576
I 18-10-17 21:43:35.281360 Node(33d9fd..()) - Connected clients: 3, cumulative: 9
I 18-10-17 21:45:25.425750 Node(33d9fd..()) Stats - Client current session traffic from V4(127.0.0.1) - 104865713
I 18-10-17 21:46:16.124052 Node(33d9fd..()) - Connected clients: 4, cumulative: 10
I 18-10-17 21:46:16.125055 This vault has received 59 Client Get requests. Chunks stored: Immutable: 0, Mutable: 13. Total stored: 5339 bytes.
I 18-10-17 21:46:16.129567 Node(33d9fd..()) Stats - Client total session traffic from V4(127.0.0.1) - 1048576
I 18-10-17 21:46:16.129567 Node(33d9fd..()) - Connected clients: 3, cumulative: 10
I 18-10-17 21:47:18.610708 Node(33d9fd..()) Expecting candidate with old name d01f31...
I 18-10-17 21:47:18.615721 Node(33d9fd..()) Our section with Prefix() accepted candidate with old name d01f31...
I 18-10-17 21:47:23.672167 Node(33d9fd..()) Sending resource proof challenge to candidate d01f31..->978b5c..
I 18-10-17 21:47:23.678684 Node(33d9fd..()) Candidate 978b5c.. passed our challenge in 5 seconds. Sending approval to our section with Prefix().
I 18-10-17 21:47:23.678684 Node(33d9fd..()) Resource proof duration has finished. Voting to approve candidate 978b5c...
I 18-10-17 21:47:23.703751 Node(33d9fd..()) Our section with Prefix() has approved candidate 978b5c...
I 18-10-17 21:47:23.704251 Node(33d9fd..()) Added 978b5c.. to routing table.
I 18-10-17 21:47:23.704251  --------------------------------------------
I 18-10-17 21:47:23.704251 | Node(33d9fd..()) - Routing Table size:   6 |
I 18-10-17 21:47:23.704251 | Exact network size: 7                      |
I 18-10-17 21:47:23.704251  --------------------------------------------
I 18-10-17 21:47:29.246989 Node(33d9fd..()) - Connected clients: 4, cumulative: 11
I 18-10-17 21:47:29.251501 Node(33d9fd..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048576
I 18-10-17 21:47:29.251501 Node(33d9fd..()) - Connected clients: 3, cumulative: 11
I 18-10-17 21:47:54.651538 Node(33d9fd..()) - Connected clients: 4, cumulative: 12
I 18-10-17 21:47:54.657053 Node(33d9fd..()) Stats - Client total session traffic from V4(192.168.1.50) - 1048576
I 18-10-17 21:47:54.657053 Node(33d9fd..()) - Connected clients: 3, cumulative: 12

Detailed logs:
Vault 1: https://pastebin.com/raw/2Dnz7kEu
Vault 2: https://pastebin.com/raw/xzLpV30H

Vault 2 has a much longer log, seems to be related to storing mutable data.

I then tried to shut down all the vaults and start them again, however now I was only able to launch the first vault. Subsequent vault failed with this error:

I 18-10-17 22:15:42.072034 [safe_vault safe_vault.rs:74] 

Running safe_vault v0.17.2
==========================
I 18-10-17 22:15:43.087736 [safe_vault::chunk_store mod.rs:122] Created chunk store at C:\Users\Warz\AppData\Local\Temp\safe_vault_chunk_store.VYWD8PmsfZJt with capacity of 2147483648 bytes.
T 18-10-17 22:15:46.113781 [routing::states::bootstrapping bootstrapping.rs:160] Bootstrapping(5a44c0..) Listener started on port 55914.
I 18-10-17 22:15:47.114441 [routing::states::bootstrapping bootstrapping.rs:287] Bootstrapping(5a44c0..) Failed to bootstrap. Terminating.
D 18-10-17 22:15:47.114441 [routing::state_machine state_machine.rs:418] State::Bootstrapping(5a44c0..) Terminating state machine

I now tried to purge safe_vault_chunk_store.* folders located at C:\Users\Warz\AppData\Local\Temp
didn’t make any difference, still not able to launch the 2nd safe vault.


#6

I’m wondering if you have a hanging safe_vault process.
Take a look in Task Manager.
image

Will you post your config contents?
Here are mine for comparison:

safe_vault.crust.config
{
  "hard_coded_contacts": [],
  "force_acceptor_port_in_ext_ep": false,
  "dev": {
    "disable_external_reachability_requirement": true
  }
}
safe_vault.routing.config
{
  "dev": {
    "allow_multiple_lan_nodes": true,
    "disable_client_rate_limiter": true,
    "disable_resource_proof": true,
    "min_section_size": 2
  }
}
safe_vault.vault.config
{
  "dev": {
    "disable_mutation_limit": true
  }
}

I’ll continue to run through some tests as well to see if I can reproduce your issue.

[UPDATE]: @warz I’m able to reproduce very easily. I’m running web API playground and running loginFromUri multiple times. Observing same error: -2000: Unexpected (probably a logic error): Could not connect to the SAFE Network


#7

@warz Well that’s interesting. I’m learning something here.
I immediately get the error after the first successful loginFromUri and I’m only running 2 vaults.
You get the error after something like 5 refreshes and you are running 5.

cc: @bochaco


#8

Here are mine:

safe_vault.crust.config
{
  "hard_coded_contacts": [],
  "tcp_acceptor_port": null,
  "force_acceptor_port_in_ext_ep": false,
  "service_discovery_port": null,
  "bootstrap_cache_name": null,
  "whitelisted_node_ips": null,
  "whitelisted_client_ips": null,
  "network_name": null,
  "dev": {
    "disable_external_reachability_requirement": true
  }
}
safe_vault.routing.config
{
  "dev": {
    "allow_multiple_lan_nodes": true,
    "disable_client_rate_limiter": true,
    "disable_resource_proof": true,
    "min_section_size": 5
  }
}
safe_vault.vault.config
{
  "wallet_address": null,
  "max_capacity": null,
  "chunk_store_root": null,
  "invite_key": null,
  "dev": {
    "disable_mutation_limit": true
  }
}

There seems to be no processes left running in task manager.


#9

My tests prove otherwise to my hypothesis that the error is related to the number of vaults.
I’m wondering now if it’s based on a max number of client connections.
I’ll get back to you. Researching where that max number is established and if we can modify it for the local test net.


#10

Further confirmation that this is expected behavior. I am now remembering this from several months back.

The following logs are from the --first vault terminal log.


There is one client connection upon execution of SAFE Browser.


An additional 2 client connections are created upon logging in and accepting authorisation for a total of 3 clients connections.


I then use API playground tool to create an app and loginFromUri to add another client connection for a total of 4.

Now when attempting another loginFromUri, following occurs in SAFE Browser’s terminal because it’s attempting to make a 5th client connection.

I know this isn’t the answer to our issue, I’m still going to get further answers about why the 4 client connection capacity, I’m just providing further documentation for you, myself, and others.


#11

Seems like you are on to something here.

The following seems a bit random and perhaps hard to reproduce. I’ll leave it here anyway, in case it may help.

I terminated all Peruse browser instances and I think that fixed my issue with not being able to bootstrap the vaults. I booted up the vaults again, and opened Peruse. This time, after finishing the final step in create account, the browser just loads “forever”. Eventually this error appears in the log:

Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1 Uncaught (in promise) Error: {"error_code":-14,"description":"Core error: Blocking operation was cancelled"}
    at Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1
    at Array.forEach (<anonymous>)
    at Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1
    at Generator.next (<anonymous>)
    at r (Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1)
    at Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1
    at new Promise (<anonymous>)
    at Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:1
    at F (Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:46)
    at Z:\executable\Peruse-v0.7.0-win-x64\resources\app.asar\webPreload.js:9

I closed the browser and tried again, now I am told that account already exists. I try to login, this time the screen is stuck loading at “Fetching registered apps”. After a long time, 5 mins maybe, I appear in the app screen, but it says " Looks like you haven‘t authorised any apps yet.". I refresh the page and it’s back in the never ending loading loop “Fetching registered apps”.

I shut down all the vaults again, i also close the node js instances running and do it again. This time I’m able to login and apps appear successfully, I refresh, and I’m logged out. Trying to login again and I get
Core error: Unexpected: Could not connect to the SAFE Network

I close the browser. And this time I am able to login just fine and I keep refreshing with no issues.

So once again I run
npm start

and go to localhost:5000

It works. I refresh more than 20 times with no issue: this is from the log:

I 18-10-18 00:16:36.628878 Node(7bb26b..()) - Connected clients: 4, cumulative: 11
I 18-10-18 00:16:46.033384 Node(7bb26b..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048997
I 18-10-18 00:16:46.033384 Node(7bb26b..()) - Connected clients: 3, cumulative: 11
I 18-10-18 00:16:51.756104 Node(7bb26b..()) - Connected clients: 4, cumulative: 12
I 18-10-18 00:16:57.191557 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.208.1) - 1048997
I 18-10-18 00:16:57.191557 Node(7bb26b..()) - Connected clients: 3, cumulative: 12
I 18-10-18 00:17:01.577719 Node(7bb26b..()) - Connected clients: 4, cumulative: 13
I 18-10-18 00:17:07.642846 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.47.1) - 1048997
I 18-10-18 00:17:07.642846 Node(7bb26b..()) - Connected clients: 3, cumulative: 13
I 18-10-18 00:17:11.625436 Node(7bb26b..()) - Connected clients: 4, cumulative: 14
I 18-10-18 00:17:14.632932 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.1.50) - 1048997
I 18-10-18 00:17:14.632932 Node(7bb26b..()) - Connected clients: 3, cumulative: 14
I 18-10-18 00:17:15.605018 This vault has received 80 Client Get requests. Chunks stored: Immutable: 0, Mutable: 14. Total stored: 5502 bytes.
I 18-10-18 00:17:21.430507 Node(7bb26b..()) - Connected clients: 4, cumulative: 15
I 18-10-18 00:17:26.067837 Node(7bb26b..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048997
I 18-10-18 00:17:26.067837 Node(7bb26b..()) - Connected clients: 3, cumulative: 15
I 18-10-18 00:17:29.588197 Node(7bb26b..()) - Connected clients: 4, cumulative: 16
I 18-10-18 00:17:32.877945 Node(7bb26b..()) Stats - Client total session traffic from V4(127.0.0.1) - 1048997
I 18-10-18 00:17:32.877945 Node(7bb26b..()) - Connected clients: 3, cumulative: 16
I 18-10-18 00:17:36.987872 Node(7bb26b..()) - Connected clients: 4, cumulative: 17
I 18-10-18 00:17:41.206595 Node(7bb26b..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048997
I 18-10-18 00:17:41.206595 Node(7bb26b..()) - Connected clients: 3, cumulative: 17
I 18-10-18 00:17:45.251350 Node(7bb26b..()) - Connected clients: 4, cumulative: 18
I 18-10-18 00:17:47.942504 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.208.1) - 1048997
I 18-10-18 00:17:47.942504 Node(7bb26b..()) - Connected clients: 3, cumulative: 18
I 18-10-18 00:17:51.872454 Node(7bb26b..()) - Connected clients: 4, cumulative: 19
I 18-10-18 00:17:56.271150 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.1.50) - 1048997
I 18-10-18 00:17:56.271150 Node(7bb26b..()) - Connected clients: 3, cumulative: 19
I 18-10-18 00:17:57.281336 Node(7bb26b..()) Stats - Client current session traffic from V4(192.168.208.1) - 104860675
I 18-10-18 00:18:00.236193 Node(7bb26b..()) - Connected clients: 4, cumulative: 20
I 18-10-18 00:18:02.608000 Node(7bb26b..()) Stats - Client total session traffic from V4(10.0.0.12) - 1048997
I 18-10-18 00:18:02.608000 Node(7bb26b..()) - Connected clients: 3, cumulative: 20
I 18-10-18 00:18:06.492833 Node(7bb26b..()) - Connected clients: 4, cumulative: 21
I 18-10-18 00:18:08.107126 Node(7bb26b..()) Stats - Client total session traffic from V4(192.168.208.1) - 1048997
I 18-10-18 00:18:08.107627 Node(7bb26b..()) - Connected clients: 3, cumulative: 21
I 18-10-18 00:18:11.745800 Node(7bb26b..()) - Connected clients: 4, cumulative: 22

Noticeably is Connected clients, it goes to connected clients: 3 when I refresh, then 4 when i click “accept”. So each refresh it loses the connection and goes back to 3 then 4 on login, and so on. I guess something caused me to reach 5 connections the other time, and now it doesn’t.

While localhost:5000 works, safe-auth://home just returns a blank page, even on refresh. I can’t get to the app screen now, even if i close the browser and login again. It always ends up here:

At least localhost:5000 works for now, as long as I only use one tab.


#12

@joshuef @bochaco This exploration may turn out to be fruitful for our MockVault issue as well as we’re seeing the same error, reproduced with the same steps both on MockVault and on a test network.
Viv pointed out that the error solely occurs in the client logs and not in the network proxy logs. Also that any proxy limit on client connections doesn’t exist and any such impl is limited to our invite server for Alpha 2.

It’s looking like the issue lies in SAFE Browser and not in any lower layer. <-- cc: @marcin

For example, after producing the error, I then execute web-hosting-manager and am able to successfully create another client connection, for a total of 5 client connections:


#13

Very interesting, although I would say we need to be careful to not confuse things here, since I believe there are probably two different issues, one error we are getting is that we cannot connect to the network (Core error: Unexpected: Could not connect to the SAFE Network), and the other one is about not being able to login as the account seems to be corrupted (Core error: Routing client error -> Account does not exist for client), in MAID-2658 I originally uploaded a mock where I was getting the former, but the other two mock files are to reproduce the latter (which were with the steps reported here in the original post by @warz ).