Dang, the original ticket Closed 4 days ago! Still occurring - lots of troubleshooting:
Issue Summary
Live Links fails to start on macOS Tahoe running on an Intel Mac. The error occurs immediately when clicking “Enable” on Live Link. This has been confirmed on a completely fresh macOS user profile, ruling out any configuration or third-party software conflicts.
Error Message
Error: read ECONNRESET
at AxiosError.from (/Applications/Local.app/Contents/Resources/app.asar/node_modules/axios/dist/node/axios.cjs:857:14)
at RedirectableRequest.handleRequestError (/Applications/Local.app/Contents/Resources/app.asar/node_modules/axios/dist/node/axios.cjs:3169:25)
at RedirectableRequest.emit (node:events:519:28)
at eventHandlers.<computed> (/Applications/Local.app/Contents/Resources/app.asar/node_modules/follow-redirects/index.js:49:24)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:105:11)
at TLSSocket.socketErrorListener (node:_http_client:518:5)
at TLSSocket.emit (node:events:519:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at Axios.request (/Applications/Local.app/Contents/Resources/app.asar/node_modules/axios/dist/node/axios.cjs:4258:41)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Log output shows:
[error] [main] LiveLinksService: Could not start Live Link Service -- {"sentryEventId":"..."}
System Details
Local Version: 9.2.9+6887
Operating System: macOS Tahoe 26.2
Architecture: Intel x64 (not Apple Silicon)
Router Mode: Site Domains
Troubleshooting Completed
All of the following were attempted without success:
Fresh Local install - Completely uninstalled Local (app + all Library files), reinstalled fresh
Fresh macOS user profile - Created brand new macOS user account, installed Local, same error
Sign out/Sign in - Re-authenticated Local account
Network testing:
No VPN active
No proxy configured
No firewall software running
Tested on home Wi-Fi and mobile hotspot - same result
Disabled “Limit IP Address Tracking” in Network settings
Disabled iCloud Private Relay
Standalone ngrok works perfectly - Running ngrok http 80 connects successfully, proving network/tunnel capability is functional
Key Finding
Standalone ngrok (v3.34.0) works without any issues on the same machine. This indicates the network stack and tunnel capability are functional - the issue is specific to Local’s internal tunnel service implementation.
Architecture Log Evidence
From Local’s startup log:
App Architecture : x64
Built for Intel : true
Running on Apple Silicon : false
Steps to Reproduce
Install Local 9.2.9 on macOS Tahoe (Intel Mac)
Create or restore any WordPress site
Start the site
Click “Enable” next to Live Link
Error appears immediately
Expected Behavior
Live Link should connect and provide a shareable tunnel URL.
Actual Behavior
Live Link fails immediately with ECONNRESET error.
Thanks for this report, @KillerDesigner! Please could you share the sentryEventId omitted from your logged output above? It might help us to narrow this down.
I just retested and I’m able to use Live Links on Local 9.2.9 under Tahoe on macOS Intel, but we’re happy to investigate further.
I’m still unable to reproduce this on Intel or Apple Silicon with Sequoia, but it could be network-specific since it affects both of your machines.
Have you tried other network connections? If you have, are you running any network filtering software (e.g. Little Snitch, corporate network filters, security software, antivirus) common to both machines?
For Live Links to work, Local needs access to hub.localwp.com. You can see if you have that from your machine by trying these steps from a terminal:
Check connection:
curl -v https://hub.localwp.com/api/
# Response should end with something like:
# Connection #0 to host hub.localwp.com left intact
Check TLS:
openssl s_client -connect hub.localwp.com:443 -servername hub.localwp.com
# Should end with:
# Verify return code: 0 (ok)
# Ctrl-C to exit.
Check DNS:
nslookup hub.localwp.com
# Should give you a 'Server' and 'Address'.
If any of those requests fail, there may be active network filtering or DNS issues from your current network. You would need to ensure Local has access to hub.localwp.com and the other URLs at ‘Allowing Local’ here:
Connection #0 to host hub.localwp.com left intact
{“errors”:[{“message”:“GraphQL Request must include at least one of those two parameters: “query” or “queryId””}]}%
SNOEmbp :: ~ » openssl s_client -connect hub.localwp.com:443 -servername hub.localwp.com
Connecting to 2606:4700:4405::6812:21d6
CONNECTED(00000005)
depth=2 C=US, O=Google Trust Services LLC, CN=GTS Root R4
verify return:1
depth=1 C=US, O=Google Trust Services, CN=WE1
verify return:1
depth=0 CN=localwp.com
verify return:1
Certificate chain
0 s:CN=localwp.com
i:C=US, O=Google Trust Services, CN=WE1
a:PKEY: EC, (prime256v1); sigalg: ecdsa-with-SHA256
v:NotBefore: Dec 19 01:12:53 2025 GMT; NotAfter: Mar 19 02:12:51 2026 GMT
1 s:C=US, O=Google Trust Services, CN=WE1
i:C=US, O=Google Trust Services LLC, CN=GTS Root R4
a:PKEY: EC, (prime256v1); sigalg: ecdsa-with-SHA384
v:NotBefore: Dec 13 09:00:00 2023 GMT; NotAfter: Feb 20 14:00:00 2029 GMT
2 s:C=US, O=Google Trust Services LLC, CN=GTS Root R4
i:C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA
a:PKEY: EC, (secp384r1); sigalg: sha256WithRSAEncryption
v:NotBefore: Nov 15 03:43:21 2023 GMT; NotAfter: Jan 28 00:00:42 2028 GMT
Server certificate
-----BEGIN CERTIFICATE-----
MIIDozCCA0mgAwIBAgIRAJ52lxz1qo4oDVqQzH22EPgwCgYIKoZIzj0EAwIwOzEL
MAkGA1UEBhMCVVMxHjAcBgNVBAoTFUdvb2dsZSBUcnVzdCBTZXJ2aWNlczEMMAoG
A1UEAxMDV0UxMB4XDTI1MTIxOTAxMTI1M1oXDTI2MDMxOTAyMTI1MVowFjEUMBIG
A1UEAxMLbG9jYWx3cC5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAQt7vx3
AzHjcxveB1hVj024f/YaHuXgC/TQXlYB0roaLVphEJzdirP02EH5i6QCKG3kha/I
rXjO+CTHexBrsPkno4ICUTCCAk0wDgYDVR0PAQH/BAQDAgeAMBMGA1UdJQQMMAoG
CCsGAQUFBwMBMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFBIQCaEDiGI76QqhJhla
I0JFGb3mMB8GA1UdIwQYMBaAFJB3kjVnxP+ozKnme9mAeXvMk/k4MF4GCCsGAQUF
BwEBBFIwUDAnBggrBgEFBQcwAYYbaHR0cDovL28ucGtpLmdvb2cvcy93ZTEvbm5Z
MCUGCCsGAQUFBzAChhlodHRwOi8vaS5wa2kuZ29vZy93ZTEuY3J0MCUGA1UdEQQe
MByCC2xvY2Fsd3AuY29tgg0qLmxvY2Fsd3AuY29tMBMGA1UdIAQMMAowCAYGZ4EM
AQIBMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jLnBraS5nb29nL3dlMS9Ic0Mz
U0JId1JFby5jcmwwggECBgorBgEEAdZ5AgQCBIHzBIHwAO4AdQAOV5S8866pPjMb
LJkHs/eQ35vCPXEyJd0hqSWsYcVOIQAAAZs0YakqAAAEAwBGMEQCIGsdg/QKicXi
O4cCsh9zWGcJ37JNEXnPKW9KVk4xB+K2AiBJPSR8XWgEb8XqPY1XrnwK94t0Fjie
QAOVcEli4oxN1wB1AEmcm2neHXzs/DbezYdkprhbrwqHgBnRVVL76esp3fjDAAAB
mzRhqTcAAAQDAEYwRAIgJuPmAdM1iMZZi3ykbaTgSTEBVos75eD7BVBPvXB81j0C
IEwEbB75G6sJI3ClKhUS4k7P4/G7sm9VYXrbGtNteZlzMAoGCCqGSM49BAMCA0gA
MEUCIQCS0oJEa7hnw6ezNYwIqw/pb3j5VikTFtwk0jPa6c886QIgUn6qBQ7+KGjp
l6iYyLEceiRqZWM/WiNGzOEN8wUGcVM=
-----END CERTIFICATE-----
issuer=C=US, O=Google Trust Services, CN=WE1
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ecdsa_secp256r1_sha256
Negotiated TLS1.3 group: X25519MLKEM768
SSL handshake has read 3912 bytes and written 1626 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Protocol: TLSv1.3
Server public key is 256 bit
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
out of frustration, since I can’t access anything I am working on, I have uninstalled LocalWP completely at this point. If there’s a “complete uninstall” script I can use to install again and log everything, that might work.
What’s weird is this was all working seemingly prior to upgrading to Tahoe. However I have also started working with a bunch of new development tools, particularly Docker Desktop and some others. And maybe they’re interfering, but I ran scripts against those ports looking for any conflicts but couldn’t find anything.
Thanks for the output, and sorry for your experience after upgrading to Tahoe, @KillerDesigner.
Your DNS/SSL/connection logs don’t appear to show any issues. I still can’t reproduce Live Links failure under Tahoe on any Macs I have access to (I also run Docker Desktop, but likely not with the exact services as you).
Port binding conflicts or local DNS resolution related to your new tools could affect Live Links. Your network connection may also play a role in traffic routing to Local’s Live Links servers.
If you’d like to continue debugging, you could try running Local from another network or with all other apps that might share ports closed. If you need them, we also have instructions to uninstall Local fully. (I recommend backing up your sites folder first if you have not already done so, though.)