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

Check the ISP

Check the browser

Still having issues? Try this:

• Switch browsers or use incognito mode: connect the agent through a different browser or open your current browser in incognito mode
• Update your browser: if the connection works in another browser or incognito, update your original browser to the latest version
• Check for interfering extensions: review your browser extensions and disable any that might block or disrupt your network connections

Stop related processes

It's a good idea to terminate agent-related processes. Here's why:

• Reset stuck processes: sometimes the agent or launcher freezes or gets stuck in a loop
• Fix resource conflicts: too many running instances can cause crashes or slowdowns
• Solve update issues: old processes might mess with recent updates or installations
• Clear glitches: stopping processes clears memory and fixes temporary bugs

macOS

 

 

Linux

Go to System monitor, select both processes below and click “End process”:

 

 

Once stopped, you can restart Multilogin for a clean, error-free session! 💻

Delete the .lock files

.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 .lock files 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, .lock files can block future attempts

Deleting .lock files is like hitting reset – it clears up the mess and lets your app run smoothly again! 

Check the ports

A busy port can be the culprit. And this is why:

• Port already in use: another process (or another agent instance) might be using the expected port
• Port conflicts: if the default port (45000) is taken, the agent will try the next available ones

What to do: 

Make sure there’s no conflict with ports starting from 45000 so the agent can run without issues! 

Windows

1. Open the Command prompt (press Win + R, type cmd, and press Enter)
2. Run the command netstat -ano | findstr :45000
3. Identify 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.

 

4. To terminate a process, run the command taskkill /F /PID {PID of the process}.

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

1. Open the Terminal
   1. macOS: Press Command + Space, type "Terminal", and press Enter
   2. Linux: Press Ctrl + Alt + T
2. Run the command lsof -i :45000
3. 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.

 

4. To terminate a process, run the command 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