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 Running Multilogin in a Docker container 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 Common errors and solutions in Multilogin 6
Multilogin X
Multilogin 6
Troubleshooting FAQ
Written by Yelena Varabyeva
Updated on August 2nd, 2024
Table of contents
Locating logs
Logs are crucial in troubleshooting technical issues. If you encounter any, make sure to send them over to support.
Logs
- Recreate the issue or prompt the error message
- Archive the logs folder located in the following directory:
- Windows:
C:\Users\%username%\mlx - macOS:
/Users/%username%/mlx - Linux:
/home/%username%/mlx
- Windows:
- Send the issue description along with the archive to support@multilogin.com
Refreshing components
Deps
This action won't cause any data loss: it will only refresh app components that allow Multilogin to work correctly.
- Disconnect the agent
- Go to the mlx folder:
- Windows:
C:\Users\%username%\mlx - macOS:
/Users/%username%/mlx - Linux:
/home/%username%/mlx
- Windows:
- Delete the deps folder
- Connect the agent and start any profile: this will trigger the components download process
Launching Mimic on Linux
Make sure you’re launching Mimic profiles under a standard user account, not with the root user. Chromium browsers, including Mimic, do not function properly when executed with root privileges.