Need to re-allow incoming Syncthing connections on every boot

[shumadrid]

Every time i boot macOS, i need to re-allow syncthing to accept incoming connections.

May be related to #233

Syncthing version: 1.29.2-2
macOS version: 15.4

[xor-gate]

I have seen it once in a while, but luckily i'm also running macOS 15 machines these days. Its a "problem" of the operating system, I have rebooted a few times last days and didn't saw this popup/nag. I'm running macOS 15.5, maybe this helps?

It is probably a enabled firewall issue. It seems I have mine turned off.

Seems I have added syncthing, but my firewall is turned off for now. But I can understand firewall disable is not possible for you.

Here an Gemini AI answers (unfortunatly):

[xor-gate]

Probably whitelisting /Applications/Syncthing is enough but it is possible the underlaying executable must be whitelisted which is under /Applications/Syncthing -> Right click in Finder -> Show Package Contents -> Navigrate to /Applications/Syncthing.app/Contents/Resources/syncthing then drag and drop the executable into the allowed firewall applications. This is necessary probably because syncthing lowercase is the actuall application not the macOS GUI. Probably to enhance it we should ask macOS to add a firewall rule instead of this manual intervention, but that would need some investigation and implementation.

[xor-gate]

[xor-gate]

This morning I have seen this notification on my macBook (second machine I have) after update of macOS and reboot on macOS 15.

[shumadrid]

Thanks for the detailed response. To be honest, I just learned to ignore this issue and just allow it on every boot.

[xor-gate]

Unfortunately the nagging is from the new macOS 15 security feature. We can not do very much about it in syncthing-macos, its a networked application and for some reason the whitelisting/allow list is not persistent. Maybe we should configure the application sandbox to use:

See also (for my own reference): https://developer.apple.com/documentation/xcode/configuring-the-macos-app-sandbox

[acicovic]

I've seen this as well, and I thought that it could be related to the issue described here.