MacOS Client has no Self-host and P2P Connectivity on macOS 27 Beta (Golden Gate)

[tangohosts]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

MacOS client doesn't want to connect to my self hosted instance where other machines don't seem to encounter any issue. Running on a MBA M2, MacOS 27.0 Beta (26A5388g), over wi-fi. Private Relay and other MAC/IP obfuscation features disabled.

MacOS Network info might point to a cause. : system info: GoOS:darwin,Kernel:Darwin,Core:27.0.0,Platform:arm64,OS:Darwin,Hostname:BMBA-M2.local,CPUs:8
error probing yamux quic://192.168.1.86:33020: open QUIC conn error: write udp [::]:57923->192.168.1.86:33020: sendmsg: no route to host
error probing yamux yamux://192.168.1.86:33010: open TCP conn error: dial tcp 192.168.1.86:33010: connect: no route to host, dur: 157.458µs

no route implies that the OS or a firewall is getting in the way, however macOS has the firewall turned off, and is on the same network node as the Windows machine which gets out fine.

AnyType macOS seemed to work fine on the first launch, however after trying to join another vault after deleting the 1st, the problem has persisted and will not change despite vault folder clears and app package clears.

AnyType macOS client works fine on my Sequoia 15.7.3 (24G419) and macOS Monterey macs. Also my other machines running Ubuntu 26 or Windows have no trouble, leading me to believe the fault is some issue with the latest beta (macOS 27) exclusively.

Expected Behavior

MacOS client requests local network access and gets allowed through whatever security mechanism macOS 27 Golden Gate is throwing out.

Steps To Reproduce

Hard to say, aberrant behavior may not be replicable without the same machine, os, and other factors.

However I broke it by just repeatedly trying to join remote and local vaults with variations in my client-config.yml

Environment

- OS: macOS 27
- Version: 56.1

Anything else?

[tangohosts]

total fail, something between the network config, and the login codes was different from the rest, I fixed this issue by ensuring the UDP/TCP ports were indeed pointed correctly, the vault-login codes were identical, and the config.yaml from a working machine was used. Now its back to working properly, at least over the internet. Local network connection still might have an issue, will report back with an edit to this reply.