Connect for macOS v3+ Troubleshooting

This article provides basic fixes for common issues with deploying Linewize Connect for macOS v3, such as:

1. Profile not pushing out correctly.
2. Incorrect profile configuration.
3. Difficulty with deploying the app proxy.

Step 1: Confirm that Connect for macOS has been installed

• Check if Connect for macOS is in the device's Applications > Family Zone folder.
• If you can’t see Connect for macOS in the Applications > Family Zone folder, find it using Search.
• If you still can’t find Connect, restart the device.
• If Connect for macOS doesn’t appear on restart, try redeploying Connect for macOS v3 through your Mobile Device Management (MDM) platform, or run the installer manually.
• If the problem persists, proceed to step 2.

Step 2: Check that the configuration profile has been installed (for MDM deployments)

• MDM deployments require the configuration profile. To verify this, open the device’s Settings and go to General > Device Management > Profile. Check that the configuration profile has been installed.

Image 1: Configuration Profile on the device.

• If you don’t see the profile, check that your device is in scope for the configuration profile for Connect for macOS v3. Next, redeploy Connect for macOS v3 again.
• If you see the profile but still have problems, proceed to step 3.

Step 3: Confirm that Network Settings are Correct

• On the macOS device, go to Settings > Network > Filters. Check that the following are available:
• FZ DNS Proxy - Running (only when the device is enrolled and WEB Filtering Mode is turned on).
• FZ App Proxy - Connected (only when the device is enrolled and WEB Filtering Mode is turned on). If the status is Not Connected, open the Connect for macOS menu bar icon and confirm that the user is enrolled. If the user is enrolled, submit the diagnostics logs to Linewize Support.
• The Family Zone Proxy should be Not Connected.

Image 2: Network settings for the proxy.

• If the Network Settings are not correct:
• Check that the user is enrolled by going to the Connect for macOS menu bar icon on the device.
• You should see the user's name and your Linewize Filter Device name.

  
  Image 3: User's name and your Linewize Filter Device name showing in Connect.

• If the Network Settings are correct, but the issue persists, proceed to step 4 .

Step 4: Check that the system extension is installed

• On the macOS device, open Terminal and run the command: 
  sudo systemextensionsctl list
• You should see the following:

Image 4: System extension showing turned on in Terminal.

• If the system extension is not installed, try reinstalling it.
• If the system extension is installed but the problem persists, proceed to step 5.

Step 5: Check the filtering mode

• On the macOS device, open a browser and go to the Diagnostics page (127.0.0.1:5770).
• In the Filtering section, check if Connect for macOS is filtering.

Image 5: Filtering section on the Diagnostics page.

• If it’s not filtering (as shown in the image above), check that Linewize Filter is configured correctly.
• Go to Configuration > Mobile Agent.
• On the Off Linewize Filter Network section, ensure the Filtering Enabled checkbox is selected.
• If the problem persists, proceed to step 6.

Step 6: Restart the System Service

• On the macOS device, open Terminal and run the command: 
  sudo /Applications/FamilyZone/MobileZoneAgent/bin/fc-system-service_darwin-amd64 --service restart
• If the problem persists, proceed to step 7.

Step 7: Submit diagnostic logs

1. On the macOS device, open Terminal and run the command: 
   sudo /Applications/FamilyZone/MobileZoneAgent/bin/fc-system-service_darwin-amd64 --service log --level debug
2. Restart the Connect service with the command: 
   sudo /Applications/FamilyZone/MobileZoneAgent/bin/fc-system-service_darwin-amd64 --service restart
3. Wait for five minutes, then open the Connect tray app (the user should be enrolled).
4. Select the Gear icon.
5. Select Submit Diagnostics.
6. Contact Linewize Support.