That is how you should interpret the “Wrong account” warning: Note: If you changed your email address to log into your LinkedIn account, you should change the email address for the existing instance that you used to log into that account previously (instead of adding a new account to Linked Helper). At the same time, instance #240328 has been never logged into any LinkedIn account (it has not logged in status) If one of the instances was archived, you should unarchive it first.Īs you can see in the picture, instance #196702 was logged in Alexander’s account before. The error message refers to the two instance IDs, namely A (#196702, previously used instance) and B (#240328, newly added instance). Linked Helper tried to log in but failed and the “Wrong account” error message appeared. He changed the email address for his LinkedIn account from to added a new LinkedIn account for to Linked Helper, and opened the newly created instance. Her LinkedIn account public ID is alexander-blackbeard-233018248 Let us look at a typical situation when a user changed the email address for a LinkedIn account and added a new instance to Linked Helper instead.
In spite of the seeming complexity of the warning, you can easily fix the problem because the cause of it is detailed in the warning itself. Hence, if you see a “Wrong account” warning, it means that you are trying to access the LinkedIn account through the wrong instance (that was used to log in to another LinkedIn account before or Linked Helper already has another instance reserved to log in targeted LinkedIn account). In this case, Linked Helper will close the current instance and will show a "Wrong account" warning. The user clicks Open, Linked Helper goes to the LinkedIn login page, enters these credentials, and finds out that they lead to the URL of the profile previously accessed through another instance or the instance a user tries to log in now was used for running another LinkedIn account before. It often happens that, despite an existing Linked Helper instance used to log into a particular LinkedIn account before, users try to add a new instance (for example, they have changed their email addresses to log into LinkedIn) or use the instance reserved for another LinkedIn account to access the targeted LinkedIn account. If I create a new empty instance #88 and try to log into either John's or Jane's LinkedIn account there, then I also will be logged out as they already have their own instances #56 and #24. In other words, if I have LinkedIn accounts of Jane and John, logged in into Linked Helper instances #24 and #56 respectfully, then I won't be able to log into Jane's LinkedIn via Linked Helper instance #56 where John was already logged in but now is logged out (or vice versa).
CREATING A LINKEDIN ACCOUNT FREE
And vice versa, you won't be able to use a certain LinkedIn account in any free / taken instance if this LinkedIn account was already logged in under a certain instance. That means you won't be able to log into a LinkedIn account via the instance where any other LinkedIn account was already logged into.
The basic rule for creating a new LinkedIn account is one LinkedIn account - one instance. Linked Helper reserves this instance for the particular account and uses it every time you open it. Wrong account warning The roots of the issueĪs you probably know from the LinkedIn Accounts menu article, when you add a new LinkedIn account, Linked Helper creates a sort of a separate browser user with its own unique set of cache and cookies, here at Linked Helper we call this an "instance".
0 kommentar(er)
