Frequently Asked Questions
Why is VPN Tracker not connecting to my IKEv2 VPN?
If VPN Tracker cannot establish an IKEv2 connection, the cause is usually a mismatch in gateway settings, authentication details, identifiers, or encryption parameters on the VPN gateway. First check that the protocol, gateway address, Pre-Shared Key or certificate, username, remote network, and identifiers exactly match the settings provided by your IT team.
The guide connect to IKEv2 VPN on Mac, iPhone, and iPad explains which details are required for IKEv2 in VPN Tracker. In addition to the hostname and login details, local identifiers, remote networks, DNS servers, and Phase 1 / Phase 2 settings may also be relevant. If the connection used to work and stopped after a macOS update, also check IKEv2 VPN not working on macOS 26 Tahoe for information about older algorithms and macOS compatibility.
If you do not manage the gateway configuration yourself, ask your IT team for the full IKEv2 settings or for a tested VPN Tracker connection. You can also contact our support team directly in VPN Tracker via Help > Contact Support, because this makes it easier to include relevant diagnostic information.
The guide connect to IKEv2 VPN on Mac, iPhone, and iPad explains which details are required for IKEv2 in VPN Tracker. In addition to the hostname and login details, local identifiers, remote networks, DNS servers, and Phase 1 / Phase 2 settings may also be relevant. If the connection used to work and stopped after a macOS update, also check IKEv2 VPN not working on macOS 26 Tahoe for information about older algorithms and macOS compatibility.
If you do not manage the gateway configuration yourself, ask your IT team for the full IKEv2 settings or for a tested VPN Tracker connection. You can also contact our support team directly in VPN Tracker via Help > Contact Support, because this makes it easier to include relevant diagnostic information.