The agent has undergone a rigorous certification process and is verified as safe and trustworthy. But you know how it is – sometimes antivirus and firewall software get a bit too jumpy and flag legitimate apps as potential threats. We can assure you that the agent is not malicious in any way, and we are committed to maintaining a safe and secure experience for our users.

Now, to tackle this glitch, try disabling those overprotective apps or whitelisting the agent.

In addition, if you have a VPN or certain proxy applications (Proxifier and SocksEscort), try to disable them too, as they may block Multilogin connections.

Check the ISP

Here's what can happen: your internet service provider might block certain websites, including Multilogin. To rule out this possibility, try connecting to a different Wi-Fi network or use your mobile hotspot. Then repeat the agent connection steps.

Check the browser

If the issue persists, it might be a good idea to connect the agent using a different browser or incognito mode. If the connection works there, update your original browser to the latest version and check if any extensions can interfere with your connection.

Stop related processes

Depending on your operating system, open Task Manager (Windows), Activity Monitor (macOS), or System Monitor (Linux) and terminate both the agent and the launcher processes.

macOS

 

 

Delete the .lock files

Check the ports

If the agent can't run, it might be because the expected port is already in use by another process, which could include another instance of the agent.

Additionally, if the default port is unavailable, the agent will try the next available port. That's why it's important to ensure no conflicts exist with the first ports after 45000.

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