Error: This browser profile is not accessible on the current version (the padlock icon)
The padlock icon instead of the “Start” button next to the name of the profile indicates that the profile is locked. There are 2 reasons that can cause the issue:
- Session lock is activated since someone from your team is currently working in this profile (this functionality isn't available in the Solo plan)
- The browser profile's core is incompatible with the current application version
You may check the reason by hovering over the padlock icon and reading the pop-up explanation why a certain profile is locked. In this article, we will discuss the cases when the browser's version and application are incompatible.
First, check the Multilogin version. The version number can be seen in the top of the main app screen.
Multilogin versions below 5.17.3
Multilogin versions 5.17.3 – 6.1.1
In Multilogin versions 5.17.3 – 6.1.1, users can see profiles with lock icons instead of “Start” buttons next to their names. After hovering over the icon, a pop-up message appears with the following warning: “This browser profile is not accessible on the current version. Please upgrade to continue using it.”
This message means that you are trying to open a browser profile that has been updated to a newer version.
To resolve the problem and launch these profiles, download and install the latest version of Multilogin (often the latest version is BETA). After that, click the green “Update” button on the right of each profile.
Multilogin version 6.2 Multicore and higher
Since a new Multicore feature allows launching browser profiles on different browser versions (while keeping the browser version of a particular browser profile consistent across teams) there are no more issues with launching old browser profiles in newer app versions.
However, if you work in a team and use multiple devices to work with Multilogin, someone can get the following error message:
This text along with a padlock icon indicates that the used app has an older version than the app where the browser profile was created, AND the apps have different browser core versions. This may happen if different Multilogin versions are used across the team.
To be able to launch the profile, you need to update the application to the latest version. In the updated app version, the padlock icon changes to the green “Update” button: