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
Stopping the agent from auto-sending log files
Written by Marcelo Brandao
Updated on October 15th, 2024
Table of contents
Feature overview
In order to improve performance and provide excellent support, Multilogin X proactively and automatically collects application-related logs (such as agent and launcher details) every six hours. These logs are stored securely on our AWS servers and are only used for support and debugging. They help improve your experience by identifying and resolving issues.
However, we understand that many users might prefer to not share their telemetry data with us. This guide will walk you through the steps to disable the automatic log upload feature for the Multilogin X agent and send them only when desired.
Disabling automatic log upload
In case it is the first time you are configuring the agent, you will need to create your own agent.yaml file.
Locate or create the configuration file agent.yaml
- Go to your local Multilogin X folder in your system:
- Windows:
C:\Users\%username%\mlx - macOS:
/Users/%username%/mlx - Linux:
/home/%username%/mlx
- Windows:
- Create a new text file using any editor (for example, Notepad)
- Rename the file to
agent.yaml
Edit the agent.yaml file
- Open the file with any text editor
- Add the following line:
AutoUploadLogEnabled: false - Save and close the file
Important notes
- This feature can only be used on agent version 1.32 or higher
-
If the
AutoUploadLogEnabledflag is not present in theagent.yamlfile, or if there is no such file in the folder, it will automatically be set totrue
Sending logs manually
You can still send logs manually directly to our AWS server at your best convenience, even if the AutoUploadLogEnabled is set to false:
- Click the Multilogin X icon in your system tray
- Choose “Send logs”
There's no need to wait for a confirmation message, the logs are automatically sent to the server.
