From: Andrew Long <andrew.longiii@gmail.com>
To: Sean Baildon <sean@baildon.co>
Cc: wireguard@lists.zx2c4.com
Subject: Re: macOS Catalina failing https
Date: Sun, 1 Mar 2020 14:28:09 -0800 [thread overview]
Message-ID: <CAKVe9vztS3LA1xc1Xz80Z9NrTvR_gi8k10YKSnneqMDh3L_bUg@mail.gmail.com> (raw)
In-Reply-To: <CAAF+QM=2cF9nV2Fq-HbUrbFbNwzw51FqAcG6RBvXv-07YWmp5Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 908 bytes --]
im not experiencing any issues on catalina, mac mini drsktop device, i
tthink fo the last 2 osX updates
On Sat, Feb 29, 2020, 03:39 Sean Baildon <sean@baildon.co> wrote:
> Hey,
>
> Recently purchased and upgraded a new MBP to Catalina.
>
> Requests to https enabled sites over the VPN no longer work, even
> using my old configuration. Requests to insecure sites—ex.
> http://example.com—work just fine.
>
> My iOS devices work as expected. I've tried using the iOS
> configurations on the laptop, but it's the same behaviour; hanging.
>
> I'm using the Mac App Store version of wireguard on a vanilla install
> of macOS Catalina. Are there any known issues? Happy to provide any
> useful debug
>
> Thanks,
> Sean
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1507 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2020-03-03 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 16:46 Sean Baildon
2020-03-01 7:08 ` Eiji Tanioka
2020-03-01 8:44 ` Barry Scott
2020-03-01 8:55 ` Barry Scott
2020-03-01 12:11 ` Rémi Lapeyre
2020-03-01 22:28 ` Andrew Long [this message]
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=CAKVe9vztS3LA1xc1Xz80Z9NrTvR_gi8k10YKSnneqMDh3L_bUg@mail.gmail.com \
--to=andrew.longiii@gmail.com \
--cc=sean@baildon.co \
--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).