Unable to authenticate communication on macOS 27 beta 3

On macOS 27 beta 3 the client immediately gives the error: “Unable to authenticate communication with background service, try restarting computer”. This occurs on multiple machines as well as with fresh installs and clients with profiles.

From the logs:

Error: connect ENOENT /var/run/pritunl.sock

at PipeConnectWrap.afterConnect \[as oncomplete\] (node:net:1705:16)

[2026-7-9 16:31:32][ERROR] Request: Client error method=POST path=/wakeup

It looks like macOS is quarantining the program:

sudo launchctl print system/com.pritunl.service

system/com.pritunl.service = {

active count = 0

path = /Library/LaunchDaemons/com.pritunl.service.plist

type = LaunchDaemon

state = not running



program = /Applications/Pritunl.app/Contents/Resources/pritunl-service

arguments = {

/Applications/Pritunl.app/Contents/Resources/pritunl-service

}



default environment = {

PATH => /usr/bin:/bin:/usr/sbin:/sbin

}



environment = {

OSLogRateLimit => 64

XPC_SERVICE_NAME => com.pritunl.service

}



domain = system

umask = 0

minimum runtime = 10

exit timeout = 10

runs = 0

last exit code = (never exited)



spawn type = daemon (3)

jetsam priority = 40

jetsam memory limit (active) = (unlimited)

jetsam memory limit (inactive) = (unlimited)

jetsamproperties category = daemon

submitted job. ignore execute allowed

jetsam thread limit = 32

cpumon = default

job state = uninitialized

sanitizer flags = 0x0



properties = keepalive | inferred program | quarantined

}

Running the commands below will fix the issue. This will be fixed in the next release possibly with a migration to SMAppService to replace the launchctl service or by applying the fix documented in the macOS 27 release notes. This should be completed in the next 1-2 weeks.

sudo xattr -d com.apple.quarantine /Library/LaunchDaemons/com.pritunl.service.plist
sudo launchctl enable system/com.pritunl.service
sudo launchctl start system/com.pritunl.service
sudo xattr -d com.apple.quarantine /Library/LaunchDaemons/com.pritunl.service.plist
sudo launchctl enable system/com.pritunl.service
sudo launchctl start system/com.pritunl.service



That didn’t seem to fix it, but sudo /Applications/Pritunl.app/Contents/Resources/pritunl-servicedid.