---
title: "The VPN server could not be found on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/vpn-server-could-not-be-found"
description: "A VPN fails with The VPN server could not be found. Check the name, DNS and the network path to the server."
---

# “The VPN server could not be found” on Mac

The Mac could not find the server from the name or address in the VPN settings. The message says to verify the server address.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: “The VPN server could not be found” on Mac. Read https://kilobat.app/guides/vpn-server-could-not-be-found.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: macOS 13 Ventura and later. The text was checked in PPPController on macOS 27.2. · Checked: 29 October 2026

## Symptoms

- System Settings › VPN shows “The VPN server could not be found.”
- The message says to verify the server address and try reconnecting.
- The status shows Connecting, then fails.

## Likely causes

- **A wrong server name.** The name has a typing error or no longer exists.
- **A DNS failure.** The Mac cannot look up the name.
- **A name that works only inside a network.** A private name does not resolve from outside.

## How to check

1. Check the server address in System Settings › VPN. Look for typing errors and extra spaces.
2. Test that the server answers. Look up its name.

   ```
   dscacheutil -q host -a name vpn.example.com
   ```
3. List the VPN services and their state.

   ```
   scutil --nc list
   ```
4. Try another network, such as a phone hotspot. If it works, the first network blocks the VPN.

## How to fix it

1. Copy the server address again from your provider.
2. Use the IP address of the server if the provider gives one.
3. Fix DNS if other names fail. See [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found).
4. Try another network.

## With Kilobat

1. Test the server name and the path to it before you try the VPN again.

   ```
   kilobat why vpn.example.com
   ```
2. The CLI is free. In the app, the advice from these checks is part of Kilobat Pro. See [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect).

## Questions

**Does a DNS change help?**

If the name does not resolve, yes. Test the name first.

**Is this a server problem?**

Not usually. The Mac did not find the server at all.

## Sources

- Error text in PPPController.bundle (SystemConfiguration), macOS 27.2 (Localizable.loctable)
- [Apple Support: Set up a VPN connection on Mac](https://support.apple.com/guide/mac-help/set-up-a-vpn-connection-on-mac-mchlp2963/mac)
- [Apple Support: Change options for L2TP over IPSec VPN connections on Mac](https://support.apple.com/guide/mac-help/change-options-for-l2tp-over-ipsec-vpn-connections-mh119412/mac)
- scutil(8), man page installed with macOS 27.2

Checked on 29 October 2026.

## Related guides

- [“The VPN server did not respond” on Mac](https://kilobat.app/guides/vpn-server-did-not-respond): The Mac sent its request, and nothing came back.
- [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found): When DNS fails, the Mac cannot change a name such as apple.com into an IP address.
- [Internal names do not resolve on a VPN](https://kilobat.app/guides/vpn-split-dns-internal-names): macOS can send queries for one domain to one DNS server and other queries to another.
- [VPN connected but no internet on a Mac](https://kilobat.app/guides/vpn-connected-no-internet): A VPN sends traffic through a tunnel.
