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 FAQConnecting the agent Testing a proxy Saving browser data Using a VPS/VPN to resolve connection issues Using Multilogin on macOS Investigating speed issues Can't start Multilogin Can't launch profile or connect to proxy Error: Failed to get profile data Stopping the agent from auto-sending log files Handling ban issues Issue: Profile is locked Troubleshooting 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
Multilogin X
Multilogin 6
Investigating speed issues
Written by Yelena Varabyeva
Updated on December 12th, 2024
Table of contents
If your profiles or app are running slowly, it might be due to poor connection. This article provides several solutions to help resolve this problem.
Slow profile speed
Check the proxy
First, create and launch a new profile without any proxy:
- If it works well, keep reading
- If it runs slowly, skip to the section “Slow interface speed”
If the profile starts to run slowly only when you add a proxy, the issue is likely with the proxy itself. Here are some solutions:
- Try a different proxy: Use a proxy with a different location, protocol type, or from another provider. Proxy speed can vary due to network infrastructure, distance from target websites, and server load. Switching proxies can help avoid these issues.
- Test your proxy in another browser: If the connection is slow in another browser with your proxy, the issue is with the proxy. Follow our detailed guide on testing it. If the connection remains slow, contact your proxy provider for further assistance.
If this step doesn't help, have a look at the solutions below.
Slow interface speed
Check the system
Make sure that your computer meets our minimum system requirements.
Check the ISP
ISP
Some internet service providers may block proxy providers, and vice versa. They may block connections to Multilogin too. To check if that is the case for you, try connecting to a VPN, another Wi-Fi network, or use mobile internet as a hotspot. This can also help if the speed of your current ISP is slow.
Check 3rd-party apps
3rd-party apps
Antivirus, firewall, VPN, and certain proxy applications (Proxifier and SocksEscort) installed on your computer may block Multilogin from working correctly and connecting to your proxy. The best option here is to uninstall such apps, but you can also try to disable them or whitelist Multilogin in their settings.
Refresh 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
Send us logs
If the issue with slowness persists, send us your proxy details (IP or hostname, port, login, and password) and logs.
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 [email protected]