iTerm2 can't reach local network after auto-update or network changes

9 views
Skip to first unread message

Harald Niesche

unread,
Dec 2, 2025, 12:08:29 AM (12 days ago) Dec 2
to iterm2-discuss
Hi,

similar to the report "Cannot reach machine on local net from shell in iTerm2 but can in Terminal - help needed!" I can't reach the local network from iTerm2, ssh reports "no route to host", but the switch under Privacy & Security / Local Network is activated and restarting iTerm2 fixes the problem.

This feels like a bug in macOS Tahoe 26.1 (the problem started after I upgraded), but Support told me to try rebooting in safe mode and, if that should fail to fix it, reinstall macOS. And since I'm unwilling to try that, I wonder if there's anything else that could be done to help with this problem.


Harald

John Simpson

unread,
Dec 2, 2025, 6:19:55 PM (11 days ago) Dec 2
to iterm2-...@googlegroups.com
On 2025-12-01, at 20:13, Harald Niesche <harald....@gmail.com> wrote:
>
> similar to the report "Cannot reach machine on local net from shell in iTerm2 but can in Terminal - help needed!" I can't reach the local network from iTerm2, ssh reports "no route to host", but the switch under Privacy & Security / Local Network is activated and restarting iTerm2 fixes the problem.
>
> This feels like a bug in macOS Tahoe 26.1 (the problem started after I upgraded), but Support told me to try rebooting in safe mode and, if that should fail to fix it, reinstall macOS. And since I'm unwilling to try that, I wonder if there's anything else that could be done to help with this problem.

The same thing happened to me over the weekend, with macOS 26.1. I ended up uninstalling iTerm, rebooting, and installing it again. When I tried to `ssh` into the local server, the OS pop-up asked for permission but the connection was blocked immediately. After clicking "OK" on the pop-up, I tried the `ssh` command again and it logged right in.

--
John Simpson - KG4ZOW
https://jms1.net/

Reply all
Reply to author
Forward
0 new messages