Troubleshooting “Boring Live Monitoring” Not Connecting

If Boring Live Monitoring is not connecting or working properly, follow the steps below to diagnose and resolve the issue. These steps will help verify the configuration in the Milestone XProtect Management Client and ensure the Event Server and URLs are correctly registered.

Step 1: Verify Event Server in Registered Services

1. Open Milestone XProtect Management Client.

2. Go to the top menu and select:
   Tools > Registered Services.

3. In the Add/Remove Registered Services window:

   • Locate the Event Server in the list.

   • Ensure the name and URL are correct.

   • Click Edit if changes are needed.

   • Ensure the http://<hostname>:22331/ URL is listed correctly and marked as Trusted if applicable.

Event Server Registered Service

Step 2: Check Site URL Configuration

1. In the Site Navigation panel of the Management Client, right-click on the site name (e.g., DESKTOP-QV2UA40) and choose Properties.

2. Under the General tab, review the URLs section:

   • The first address listed should match the Management Server address.

   • If it shows an IP address or incorrect hostname, click Add and enter the correct server name.

   • You can then remove the incorrect one if needed.

Example: If the correct server is DESKTOP-QV2UA40, make sure the first URL is http://desktop-qv2ua40:80/.

Site URL Configuration

Step 3: Restart Required Services

If changes were made to the URLs or Event Server registration:

1. Restart the following Windows services on the Management Server:

   • Milestone Management Service

   • Milestone Event Service

2. Then, restart the Boring Live Monitoring Windows Service.

Step 4: Collect Logs If Issue Persists

If Boring Live Monitoring is still not connecting after the above steps, gather the latest logs and send them to support@theboringlab.com:

• Milestone Event Server logs:
  C:\ProgramData\Milestone\XProtect Event Server\logs

• Boring Live Monitoring logs:
  C:\ProgramData\The Boring Lab\Live Monitoring\Logs

Email these log files to us for further analysis.