No network access in macos 27

[powskierman]

Issue Description

macOS 27 blocks LAN connections from Ghostty 1.3.1 child processes.

In Ghostty:
ssh mlapoint99@192.168.0.100
=> ssh: connect to host 192.168.0.100 port 22: No route to host

The identical command succeeds in Terminal.app. The Mac has a valid route over en0. Ghostty declares NSLocalNetworkUsageDescription, but never receives a permission prompt and is absent from System Settings > Privacy & Security > Local Network. Reinstalling Ghostty and tccutil reset LocalNetwork did not resolve it.

Expected Behavior

Ghostty should not block LAN connections from child processes.

Actual Behavior

Ghostty can’t connect to my server.

Reproduction Steps

➜ ~ ssh mlapoint99@192.168.0.100
ssh: connect to host 192.168.0.100 port 22: No route to host
➜ ~

Ghostty Logs

Ghostty:
➜  ~ ssh mlapoint99@192.168.0.100
ssh: connect to host 192.168.0.100 port 22: No route to host
➜  ~
Terminal:
MacBook-Pro:~ michel$ ssh mlapoint99@192.168.0.100
mlapoint99@192.168.0.100's password: 
Linux bambuddy 6.18.34+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.18.34-1+rpt1 (2026-06-09) aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jul 26 09:33:55 2026

Ghostty Version

➜  ~ ghostty +version
Ghostty 1.3.1

Version
  - version: 1.3.1
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseFast
  - app runtime   : .none
  - font engine   : .coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue
➜  ~

OS Version Information

macos 27

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

not relevant

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[craig-miller]

I can confirm this exact description.

macOS 27 Beta 4, latest Ghostty 1.3.1 via homebrew. Can connect via terminal, but no route to host with Ghostty. Ghostty doesn't appear in Privacy and Security - Local Network Network to be toggled on.

[shaun-haem]

Can confirm.

I think there is something different in how the beta is handling security for terminal apps globally (outside of the MacOS default one) because a similar issue with Kitty and Terminus (so even an app from the Mac App Store doesn't fair any better right now).

[bo2themax]

Duplicate of #13438

[pratikngupta]

I experienced the same issue across multiple applications (Warp, iTerm2, VS Code, and Ghostty) running macOS 27 Developer Beta.

Deleting the network configuration PLIST files and re-approving permissions fixed the issue. Because these files are protected by System Integrity Protection (SIP) on modern macOS versions, you need to temporarily disable SIP to remove them.

Instructions

1. Boot into Recovery Mode

   • Restart your Mac mini and press and hold the Power button until the startup options screen appears.
   • Select Options to enter macOS Recovery.

2. Disable SIP Temporarily

   • From the top menu bar, open Utilities > Terminal.
   • Run the following command and then restart the mac normally

csrutil disable

3. Delete Network Cache Files
   • Open your standard terminal application and execute the following commands to clear the corrupt network permission caches:

sudo rm /Library/Preferences/com.apple.networkextension.plist
sudo rm /Library/Preferences/com.apple.networkextension.uuidcache.plist

4. Re-enable System Integrity Protection
   • Reboot back into Recovery Mode.
   • Open Utilities > Terminal and re-enable SIP > then restart the mac normally

csrutil enable

---

I have tried the above steps on following MacBook and all the apps where working again after resetting the network configuration PLIST.

1. Macbook Air M1
2. Macbook Pro M5 pro

I hope this is temporary solution, and apple fix the underlying issue that is causing the plist file to corrupt.