If browser profiles fail to start on a Linux server, first test the profile with a direct local API request. If the manual launch works, compare your API parameters with the working profile settings. If it fails, check the agent logs, SSL/TLS errors, and your Xvfb/headless setup.

➡️ Keep the Multilogin desktop app running, or connect the agent if you use the web interface → start the same browser profile with curl → check the result → review logs if it fails.

Before you start

Make sure:

• Multilogin desktop app is running, or the agent is connected if you use the web interface
• You know the browser profile’s folder_id and profile_id
• You can run curl commands on the Linux server
• Xvfb is installed if you are using headless mode

Launch profiles manually

1. Launch Terminal
2. Run the following command (replace folder_id and profile_id respectively):

   curl -X GET https://localhost:45000/api/v2/profile/f/<folder_id>/p/<profile_id>/start

3. Check if the profile launches successfully

Expected result: the profile starts successfully and the API returns the start response.

• If the manual curl request works, the Linux environment and local launcher are likely working. Compare the failing automation request with this working request.
• If the manual request fails, continue with the log, SSL/TLS, and headless checks below.

Locate and analyze agent logs

1. Go to one of the following directories:
   1. /opt/usr/mlx/
   2. /home/%username%/mlx/logs
2. Look for launcher_<date>.log and agent_<date>.log

Investigate SSL/TLS errors

1. Check for “Bad record MAC” errors in the logs: SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC
2. Make sure that the Linux server's OpenSSL configuration is correct

Compare API and UI behavior

1. If launching via the UI works, but API fails, check API parameters and UI settings (they should match)
2. Test using the same profile ID and settings manually via curl

Check Linux environment setup

1. Make sure that Xvfb is installed and properly configured for headless mode. Refer to the following articles for more details: 
   1.  How to connect the agent in Multilogin (connection on Linux headless)
   2. Configure the agent for headless mode and auto-launch in Linux
2. Confirm that the Multilogin agent or app is running and accessible via the correct port (refer to the step from the following article: How to fix agent connection issues)

Nothing works?

If the issue persists, send us your log files, and we will investigate it further for you.

1. Recreate the issue or wait until the error message appears
2. Archive the logs folder found in this location:
   /home/%username%/mlx
3. Email support at [email protected] with:
   1. A clear description of the issue
   2. The archived logs folder attached