EAP/PEAP Wi-Fi connection stuck in "Connecting" state: use "Do Not Validate" for CA Certificate when no server certificate is required

Android

If your Esper-managed device is stuck in a "Connecting" state when attempting to join an EAP/PEAP Wi-Fi network, the issue may be a mismatch between your Wi-Fi profile configuration and what your network actually requires. This article explains how to fix it by adjusting your CA Certificate settings.

Before you begin

Verify that your network does not require CA certificate validation. Check your network operator's Android setup instructions—if they specify "Do Not Validate" for the CA Certificate field, this article applies to you. If your network requires CA validation, contact your network administrator for the correct certificate format and path.

Step 1: Update your Wi-Fi profile settings

1. In the Esper Console, go to Blueprints → [Your Blueprint Name] → Wi-Fi → [Network Name] → Edit.
2. Locate the CA Certificate field.
3. Set it to "Do Not Validate" or leave it blank. Do not specify a certificate file path.
4. Click Save.

Step 2: Confirm your other EAP settings

Verify that the remaining EAP configuration matches your network operator's requirements exactly:

• EAP Method: PEAP (or your network's required method)
• Phase 2 Authentication: MSCHAPv2 (or your network's required method)
• Identity: Your username (for example, IoT-Radio)
• Anonymous Identity: Leave blank
• Password: Your network password

If any of these settings differ from your network operator's instructions, update them now.

Step 3: Publish and apply the updated Blueprint

1. Click Publish to save your changes.
2. Apply the updated Blueprint to your test device or device group.

Step 4: Verify the connection on your device

1. Wait a few moments for the Blueprint to sync to your device.
2. On your device, check that the Wi-Fi network transitions from Connecting to Connected.
3. In the Esper Console, go to Devices & Groups → [Device Name] → Activity Feed and confirm that the network profile was applied without errors.

Step 5: Roll out to your full fleet

Once you confirm the connection works on your test device, apply the updated Blueprint to all remaining devices in your fleet.

Troubleshooting

Test on a non-managed device first

If the device still cannot connect, manually connect a standard Android device (not managed by Esper) to the same network using your network operator's instructions with "Do Not Validate" selected. If that device also fails, the issue is with your network configuration or credentials, not Esper.

If your network requires CA certificate validation

If your network operator specifies that CA validation is required, confirm the following:

• The certificate file is in a format compatible with Android (.cer, .pem, or .der).
• The certificate has been pushed to the device via Esper Content Management before the Wi-Fi profile attempts to reference it.
• The file path in your Wi-Fi profile matches the path where the certificate was delivered.

If timing issues occur between certificate delivery and profile application, contact Esper Support for assistance with sequencing.

Check if your profile is being applied

If you suspect the Wi-Fi profile is not reaching your device at all, connect to your device via ADB and run:

adb logcat -s Esper Agent

Review the logs for any errors related to the Wi-Fi or EAP profile. If you see no profile application activity, contact Esper Support.

Still need help?

If your device remains stuck in a "Connecting" state after following these steps, or if you need assistance with CA certificate configuration for your specific network, submit a support ticket. Include the device model, Android version, your EAP method, your network SSID, and a screenshot of your current Wi-Fi profile settings.