IBM Support

Resolve MEG "Failed to Start gateway" Error

Fix Readme


Abstract

For environments encountering "Failed to Start gateway" error after upgrading to the new MEG service for intranet sites on iOS devices. Follow the steps in this article to resolve the error without having to disable the new service, which is required for ongoing support of MEG features on iOS devices with Secure Browser.

Content

MEG customers are reporting that MaaS360 Browser is unable to connect to MEG VPN. The error they are seeing in the MaaS360 Secure Browser is "Failed to start gateway".

Root cause

MaaS360 gateway is configured with a connection rule to launch MaaS360 gateway when MaaS360 Secure browser access maasvpntestingondemand.com and the domain is not reachable from the network end user is using the device. This domain is always expected to return not found error on dns lookups but the address is resolving to a valid IP -address starting dec 14th. As a result of this domain status change, the MaaS360 gateways is failing to start.

Resolution

Override the value by using advanced attribute in policy.

Step 1: Configure the advance configuration parameter in the Persona policy and push the policy to device.

CRMEG3InvocationHost with value maas360gwlaunchprobe.maas360.com 
Screen shot of advanced settings in persona policy

Step 2: Agent (MaaS360 App / MaaS360 Browser)

1. Make sure that the MaaS360 Browser and MaaS Agent are stopped from the settings or swiping up on the apps from the home screen.
2. Launch MaaS360 Agent first.
3. Make sure the new persona policy is applied on to the device.
4. MaaS Agent will prompt to push new NEW VPN profile to the device. Accept that prompt show by iOS.
5. This will override the old VPN profile with on demand connection rule to maas360gwlaunchprobe.maas360.com 6. Now launch MaaS360 Secure Browser.

7. Open the website with which is allowlisted in gateway filter.
8. MaaS360 Browser will show connecting gateway prompt followed by auth prompt based on the auth configuration in persona policy.

Additional fixes:

The default value in MaaS360 core app and MaaS360 Browser will be modified to use new on demand connection Rule. This change will be available in MaaS360 Agent 4.81.3 & MaaS360 Browser v3.60.30.
Values in configured in policy will take precedence over default values and changes made to customers in Step 1 will still be respected even after agents are upgraded.

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m0z0000000717AAA","label":"MOBILE ENTERPRISE GATEWAY"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
21 December 2021

UID

ibm16527918