@happybeing @Mindphreaker , the number of clients can connect at a time is limited to four, let me explain in more detail how you should count them so you know when you are hitting that limit.
When the browser is launched, the Authenticator plugin is loaded, it will create a connection to be able to either register you on the network if you are creating an account or to check the credentials upon an login. This will consume the first client (1 out of 4 allowed clients).
After you logged in, you will see that an authorisation request pops up, this is the browser itself trying to register as a SAFE app to then be able to fetch/save the state, i.e. your bookmarks and browsing history. This information was stored locally before, but since it’s private information we thought it’s better to store it only on the SAFE network within your account. Therefore the browser needs to have your authorisation to connect and be able to store this data on your SAFE account. If you are wondering now what’s the difference between this and any other SAFE app requesting access, the answer is simply “there is no difference at all, it’s just a SAFE app, just embedded in the browser”. Therefore, if you authorise the browser app you are using one more connection (2 out of 4 now).
At this point, you may be trying to open up a safesite, so you open a tab and enter a URL, this is when the safe-app-plugin creates its connection to be able to fetch the site. This will be a single connection used by the safe-app-plugin to fetch all safesites no matter how many tabs/sites you open. In this case the connection is an unregistered connection, i.e. a read-only connection to the network to read only data publicly available, and this is why there is no authorisation request for the user, but it still counts as a client connection. This becomes your third connection (3 out of 4).
When you open a safesite, this can either be a static site which doesn’t use the DOM API so it doesn’t need a connection. But it can be a dynamic site/webapp which does connect to the network either unregistered or registered (it needs user authorisation). As an example of this, the safe://chaty.test app creates an unregistered connection upon being loaded to fetch the chats list, and it closes it and re-opens a new connection (this time a registered connection) when you hit the button to send a message. Therefore, in our scenario, an app like this will have the fourth available connection whilst its tab is open (4 out of 4).
If you try to open any other app which creates a connection, regardless if it’s opened form the browser, a desktop app, (ohh!..I almost forget about this, but now I also have to include it here in the explanation) or from a mobile app 
, you should get a connection error since you’ve reached the limit already. So at this point you can close any of the apps that is using a connection to free it, and then be allowed to connect with another app.
As you can imagine, you can decide to not allow the browser app if you are not interested in storing the browsing history or bookmarks on your account, and that would allow you to have one less connection used and available for other app. Or you could avoid opening a safesite so the plugin never creates its own connection if you are trying to play with desktop apps.
The main purpose of this explanation is so you can realise if the issue is due to the clients’ limit, or perhaps an invalid/non-white-listed IP, or something else.
Does this limit really has to be so strict?
