Development discussion of WireGuard
 help / color / mirror / Atom feed
From: David J Chapper <dchapper@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: MacOS Mojave - Tunnel activation failure
Date: Thu, 30 Jan 2020 19:59:51 -0600	[thread overview]
Message-ID: <6A512C85-276D-4060-9F5B-7F5AA42962B8@gmail.com> (raw)
In-Reply-To: <CAHmME9rEvnonTMZ95AyK1F1o2mwnBD06NkbVZ3prvz2nBSg1ng@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1381 bytes --]

Hello, hoping someone else has experienced this and resolved the issue.

The Wireguard app has been running without issue for many months until today when I attempted to activate the tunnel and received the following error:

“Activation failure” Unable to retrieve tunnel information from the saved configuration.

If I try and edit the config the app crashes. Some details from the problem/crash report:

Process:               WireGuard [48844]
Path:                  /Applications/WireGuard.app/Contents/MacOS/WireGuard
Identifier:            com.wireguard.macos
Version:               0.0.20191105 (16)
App Item ID:           1451685025
App External ID:       833476010
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           WireGuard [48844]
User ID:               502

Date/Time:             2020-01-30 19:46:52.417 -0600
OS Version:            Mac OS X 10.14.6 (18G2022)
Report Version:        12
System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [48844]



[-- Attachment #1.2: Type: text/html, Size: 9673 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2020-02-07 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 12:15 wireguard ci hooked up to quite a few kernel trees Jason A. Donenfeld
2020-01-29 12:23 ` Bhaskar Chowdhury
2020-01-29 12:57   ` Michael B. Williams
2020-01-29 12:40 ` dvn
2020-01-29 12:44   ` Jason A. Donenfeld
2020-01-31  1:59     ` David J Chapper [this message]
2020-01-29 15:32   ` Joe Doss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A512C85-276D-4060-9F5B-7F5AA42962B8@gmail.com \
    --to=dchapper@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).