How to fix agent connection issues
Multilogin agent has been thoroughly certified and verified as safe and trustworthy. Sometimes, though, antivirus or firewall software can mistakenly flag legitimate apps like this as threats – but we promise it’s not malicious.
How to fix it:
- Disable or whitelist the agent in your antivirus or firewall settings
- Turn off VPNs or proxy tools like Proxifier and SocksEscort, as they may block Multilogin connections
Learn more in the article How to fix Multilogin issues caused by antivirus, VPNs, and more.
Check the ISP
ISP
Sometimes, internet service providers (ISPs) block proxy providers or even Multil
Sometimes, internet service providers (ISPs) block proxy providers or even Multilogin itself. Here’s how to test and work around it:
- Try connecting through a VPN: this can bypass ISP restrictions
- Switch networks: use a different Wi-Fi, or turn your phone into a hotspot with mobile data
- Check your speed: if your current ISP is slow, changing networks might also improve performance.
If the issue resolves with these steps, it’s likely your ISP causing the trouble.
Check the browser
Still having issues? Try this:
- Update your browser: if the connection works in another browser or incognito, update your original browser to the latest version
- Switch browsers or use incognito mode: connect the agent through a different browser or open your current browser in incognito mode
- Check for interfering extensions: review your browser extensions and disable any that might block or disrupt your network connections
Stop agent and launcher processes
Sometimes an old agent or launcher process gets stuck in the background.
-
Open:
- Task Manager on Windows
- Activity Monitor on macOS
- System Monitor on Linux
- Find the Multilogin agent and launcher processes and stop them
- Then reopen Multilogin and try again
Windows

macOS

Linux

Delete .lock files
.lock files
.lock files are temporary files apps make to show a file or resource is in use. H
.lock files are temporary files apps make to show a file or resource is in use. Here's why you can delete them:
-
Fix stuck apps: if an app crashes, leftover
.lockfiles can trick the system into thinking it’s still running - Stop errors: these files might block your app from starting or working properly
-
Clear update problems: if an update or sync gets interrupted,
.lockfiles can block future attempts
Deleting .lock files is like hitting reset – it clears up the mess and lets your app run smoothly again!
Windows
- Stop all running profiles
- Close the desktop app 🖥️ or disconnect the agent if you're using the web interface 🌐
- Go to the mlx folder in your user folder: C:\Users\%username%\mlx
- Delete all the
.lockfiles

macOS
- Stop all running profiles
- Close the desktop app 🖥️ or disconnect the agent if you're using the web interface 🌐
- Go to the mlx folder in your user folder:
/Users/%username%/mlx - Delete all the
.lockfiles

Check the ports
The agent starts with port 45000. If that port is already busy, it can try the next available port.
Windows
- Open the Command prompt (press Win + R, type cmd, and press Enter)
- Run the command
netstat -ano | findstr :45000
netstat -ano | findstr :45000
- Find the PID (Process ID) associated with the processes running on port 45000
If this command doesn't return any processes, it means the port is not in use and the issue is caused by something else. Skip to the next step.
- To terminate a process, run the command
taskkill /F /PID {PID of the process}
taskkill /F /PID {PID}
Make sure to replace "{PID of the process}" with the actual PID you got in step 3. Repeat the steps for ports 45001, 45002, etc, if needed.

macOS and Linux
- Open the Terminal
- macOS: Press Command + Space, type "Terminal", and press Enter
- Linux: Press Ctrl + Alt + T
- Run the command
lsof -i :45000
lsof -i :45000
- Look for the PID (Process ID) associated with the processes you want to terminate.
If this command doesn't return any processes, it means the port is not in use and the issue is caused by something else. Skip to the next step.
- To terminate a process, run the command
kill -9 {PID of the process}
kill -9 {PID of the process}
Make sure to replace "{PID of the process}" with the actual PID you obtained in step 3. Repeat the steps for ports 45001, 45002, etc, if needed.

Restart the device
Sometimes, a fresh start works wonders.
If the steps above didn't do the trick, try giving your device a quick restart and then go ahead with the agent connection steps again.
Nothing helps?
Send us your logs and we’ll take a closer look.
Logs
Recreate the issue or prompt the error message Archive the logs folder located in
- Recreate the issue or wait until the error message appears
- Archive the logs folder found in these locations:
-
Windows:
C:\Users\%username%\mlx -
macOS:
/Users/%username%/mlx -
Linux:
/home/%username%/mlx
-
Windows:
- Email support at [email protected] with:
- A clear description of the issue
- The archived logs folder attached









