Contact Us
If you still have questions or prefer to get help directly from an agent, please submit a request.
Popular topics: Multilogin X, Multilogin 6,
-
Retrieving the token Using the automation token in a workspace Retrieving profile, folder, and workspace IDs Retrieving the user ID Selenium automation example Playwright automation example Puppeteer automation example Logging in to Multilogin automatically Setting up automatic cookie collection Auto-launching the agent Exporting proxy details from profiles Converting external proxy lists into API-ready JSON files Automation FAQ
-
Error: Failed to get IP data: can't connect through proxy Error: Javax.crypto.badpaddingexception: pad block corrupted Status: Update in progress...Loading (1) of 2 components Error: Fingerprint composition failed Connection error due to non-Latin characters in Windows username Error: Mimic/Stealthfox executable is not found Multilogin 6 browser profile shows "Error" in status Can't launch a profile in Multilogin 6 JavaScript error when switching to dark mode in Multilogin 6 Common errors and solutions in Multilogin 6
Core updates and how they work
Written by Lena Karavaeva
Updated on July 27th, 2024
Table of contents
Keep track of the latest core updates in our release notes or in the official Multilogin Telegram channel.
In Multilogin, we normally provide new browser core versions with one- or two-week delay from their official release. The cores are then updated automatically on profile launch. In this article, we will explain why such delays are actually useful.
Why it is better to wait
In the world of online privacy, staying ahead of the curve is paramount. So, when Chrome or Firefox roll out their new browser core, your first thought is to, probably, update your antidetect right away.
However, it is a common misconception. Updating the browser core to the latest version immediately upon its release is not the best practice. Here's why.
- Vulnerability issues: The official Chrome/Firefox core release often serves as a testing ground for new features and security patches. While they are intended to enhance user experience and security, it is best to adopt them after thorough testing and refinement are done by the publisher 🕵️
- Possible bugs: Delaying the update allows developers to observe and address any potential issues that may arise following the official release. This proactive approach minimizes disruption for users and ensures a smoother transition to the updated core 🐞
- Bans and restrictions: Some websites do not incorporate the new cores right away. Updating the core too quickly may lead to unexpected results and account restrictions. By waiting for the wider adoption of the new core, you can ensure compatibility and reduce the risks of being detected 🛑
- Automation compatibility: Tools like Puppeteer, Selenium, and other web-scraping or testing frameworks rely heavily on browser functionalities. They frequently experience compatibility issues with the latest cores and need time to adjust their APIs and features accordingly 🤖
Troubleshooting
Normally, a browser core should be downloaded within 10 minutes. Here's what you can do if this process is taking longer than expected:
- Uninstall 3rd party apps: Antivirus, firewall, VPN, and proxy apps (such as Proxifier and SocksEscort) may interrupt Multilogin connections
- Change your internet connection: Your ISP may block certain websites, including Multilogin – to rule out this possibility, try connecting to a different Wi-Fi network or use a mobile hotspot
- Reconnect the agent: This can help if related processes have been interrupted and are not running correctly
- Reinstall the app components: This way the app will download all the necessary components for smooth operations (you won't lose any data)
- Check your system language: In some cases, the download process can be stuck if your OS language is not English