Alpha2 connection issues

I’ve been getting increasing issues connecting to alpha2. Yesterday I was using SB 0.14.0 but having updated to 0.14.1 I’m having the same problem.

Yesterday I thought maybe I was using up connections because I was creating a new account, using WHM to create a website and then using SAFE Drive to upload to it. So I spread those activities out and it seemed to help.

But today I’m just setting IP, starting the browser, logging in, enabling experimental APIs and then trying the webid manager. It was stalling at enabling the experimental APIs (with a popup warning me to check my IP is set), but now I get past that but when I try to open the webid manager I’m getting a page with the message.

The browser console shows the following in a couple of places, each followed by a bunch of I 19-08-04 14:26:16.849725 Bootstrapping(e7f815..) Connection failed: The chosen proxy node already has connections to the maximum number of clients allowed per proxy. I 19-08-04 14:26:16.851109 Bootstrapping(e7f815..) Lost connection to proxy PublicId(name: 9b8f4d..). ... messages:

I 19-08-04 14:26:16.849725 Bootstrapping(e7f815..) Connection failed: The chosen proxy node already has connections to the maximum number of clients allowed per proxy.
I 19-08-04 14:26:16.851109 Bootstrapping(e7f815..) Lost connection to proxy PublicId(name: 9b8f4d..).

I had shut down the browser while writing the above, and when I restarted it and tried to log in it failed with Core error: Unexpected: Could not connect to the SAFE Network displayed underneath the Account Secret input field.

After waiting a few minutes, without restarting the browser I was able to log in ok. When I enabled the experimental APIs I got the warning popup which says Error / Check your current IP address matches your registered address at invite.maidsafe.net but the WebID manager menu is there (no WebIDs on this account yet.

So now I Launch WebidManager and this time it loads ok and I am able to create an id.

Solution? I guess the workaround is to wait a few minutes when it seems to be giving errors.

5 Likes

Seems like an overload issue in my unexperienced view, maybe with all the mobile apps?

2 Likes

Thanks for flagging this. Seems like it was just a temporary glitch, hopefully we won’t see it again. Also, just to let you know, the QA team check the health of the Alpha network on a daily basis to ensure that all nodes are online and the proxy nodes are correctly dispersed. Please do flag any repeats of this kind of issue.

6 Likes

It was much better later yesterday - or I’m getting used to how to handle it. Not sure. But it is still happening - it worked ok this morning for a couple of hours but happened again just now so I’m pausing for a few mins.

When it happens I’ve learned to close the browser, wait a while and then try again. Just closing WHM for example didn’t seem to help.

Update: and now I’m in again. :smile: … but STILL FLAKEY. After enabling Ex UI I can’t access my WebIDs and it suggests I check my IP.

I’m trying to debug some problems that appear when authenticating on the live network (ok on mock), but this is making that difficult. I’ve had the browser view die and the browser (0.14.1) crash once, and now I appear to be getting an error thrown after a successful return from appHandle.auth.loginFromUri() the error being:
Could not connect to the SAFE Network", stack: "-2000: Unexpected (probably a logic error): Could …s/@maidsafe/safe-node-app/src/api/auth.js:538:22)

I think this is going to prevent me working effectively on this because it takes a lot of uploads, PUTS on account, time waiting etc. So I might have to leave the Solid on SAFE live demos now until Fleming and new APIs.

It’s a shame because it works on mock, although I have been able to show Solid Filemanager at least.

5 Likes

Sounds like good old port exhaustion. There are a few ways to fix it that I have seen, Increase the port span @ the kernel level, kernel tcp connection reuse settings, also ensure client keep-alive is allowing the connections to persist thus reducing ports in timed wait.

5 Likes

OK, thanks for the update. We (QA team) are going to look into it from the Alpha network side of things, ensure there are no issues with the proxy servers.

6 Likes

@happybeing I believe I’ve resolved the issue you were having here - I cleared out the huge list of client connections which had grown pretty big over the last year. Looking at your log entries above, and the logs on the proxies themselves, it all pointed to this being the root cause.

I see from another post that you may be pausing Solid on SAFE work for now, if you do come back to it then let me know if you see this error again.

6 Likes

Thanks @StephenC I may review my decision but maybe not for a few days. There’s one issue I’d like to crack before letting go so this is great news.

4 Likes

Hi @StephenC, I’m still having some problems. These may be specific to my machine as I tend to keep a lot of stuff running and don’t reboot for weeks, but even if that’s the cause I think logging the symptoms will be useful.

Right now I have a reproducable issue:

  • ensure IP is set
  • start SB 0.14.1
  • login
  • accept browser auth request
  • enable experimental APIs
  • accept auth request [I don’t always get this]

At this point I go to the WebID menu and it shows ‘No webids found’ and is NOT showing updating. I then get the popup with:

Error

Check your current IP address matches your registered address at invite.maidsafe.net

After this the webids menu shows ‘Updating WebIds’ but it never completes.

In the past restarting the browser a couple of times might get me past this but not today on this account. I’ve tried closing some stuff down on my laptop but the issue still repeats. I was able to get past this point on a different account earlier.

The browser console shows:

I 19-08-12 15:18:57.759462 Failed to Bootstrap with 138.68.181.242:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:18:57.767029 Failed to Bootstrap with 138.68.189.15:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:20.727697 Failed to Bootstrap with 138.68.181.86:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:27.669982 Failed to Bootstrap with 138.68.181.243:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:28.112272 Bootstrapping(276eb0..) Connection failed: The chosen proxy node already has connections to the maximum number of clients allowed per proxy.
I 19-08-12 15:19:28.113478 Bootstrapping(276eb0..) Lost connection to proxy PublicId(name: 27ef49..).
I 19-08-12 15:19:29.260525 Failed to Bootstrap with 138.68.181.168:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.264818 Failed to Bootstrap with 138.68.181.180:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.269145 Failed to Bootstrap with 138.68.181.182:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.270664 Failed to Bootstrap with 138.68.181.176:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.272417 Failed to Bootstrap with 138.68.181.57:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.276759 Failed to Bootstrap with 138.68.185.218:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.277945 Failed to Bootstrap with 138.68.181.242:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.278776 Failed to Bootstrap with 138.68.189.15:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.280640 Failed to Bootstrap with 138.68.189.14:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.281234 Failed to Bootstrap with 138.68.181.179:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.283090 Failed to Bootstrap with 138.68.181.87:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.294544 Failed to Bootstrap with 138.68.181.243:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.299130 Failed to Bootstrap with 178.62.76.8:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.300022 Failed to Bootstrap with 138.68.181.86:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.300719 Failed to Bootstrap with 138.68.181.60:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:29.302100 Failed to Bootstrap with 138.68.181.249:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:38.116381 Bootstrapping(276eb0..) Failed to bootstrap. Terminating.
I 19-08-12 15:19:58.821434 Failed to Bootstrap with 138.68.185.218:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:19:58.822588 Failed to Bootstrap with 138.68.181.182:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.204906 Failed to Bootstrap with 138.68.185.218:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.237146 Failed to Bootstrap with 138.68.181.86:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.237514 Failed to Bootstrap with 138.68.181.179:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.237758 Failed to Bootstrap with 178.62.76.8:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.237981 Failed to Bootstrap with 138.68.181.180:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.238203 Failed to Bootstrap with 138.68.181.242:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.238580 Failed to Bootstrap with 138.68.181.176:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.239111 Failed to Bootstrap with 138.68.181.243:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.239397 Failed to Bootstrap with 138.68.189.15:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.239650 Failed to Bootstrap with 138.68.181.249:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.239894 Failed to Bootstrap with 138.68.181.182:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.240128 Failed to Bootstrap with 138.68.181.87:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.240348 Failed to Bootstrap with 138.68.189.14:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.240638 Failed to Bootstrap with 138.68.181.60:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.240935 Failed to Bootstrap with 138.68.181.57:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:23.246959 Failed to Bootstrap with 138.68.181.168:5483: (ClientNotWhitelisted) Our Client is not whitelisted
I 19-08-12 15:20:32.114231 Bootstrapping(95ffb6..) Failed to bootstrap. Terminating.
2 Likes

Ah damn, ok thanks for posting the details @happybeing, leave it with me to see if we can find an explanation for this

3 Likes

NOTE: This is not really an issue for me as we move to Fleming so don’t prioritise on my account. I’m happy to continue with mock (old) and start to move to the new APIs as they become available.

Small update: I’ve been continuing to have problems, even immediately after rebooting so it doesn’t appear to be machine state.

Example:

  • reboot (Ubuntu 18.10)
  • Gnome starts
  • update IP address with invite for relevant account
  • open terminal and start SB 0.14.1
  • login to an account I set up to test solid-filemanager
  • open a tab, browse to safe://dweb
    [all ok to this point]
  • click enable experimental APIs
  • get connection warning popup
  • close dweb tab and open a new tab
  • click on WebIDs drop down - it permanently displays ‘no webids found’

[accepting auth requests along the way]

I think the above is right although I typed it from memory!

TLDR; I can no longer do stuff with experimental APIs at least on the accounts I’m working with.

If you want to try with that account let me know and I’ll PM the credentials.

2 Likes