# New connection behavior with macOS client v1.3.4059.45

**URL:** <https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549>\
**Category:** Pritunl VPN\
**Tags:** pritunl-client\
**Created:** [October 28, 2024, 11:25am UTC](https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549 "2024-10-28T11:25:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thawthorn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/thawthorn/32/1023_2.png) [@thawthorn](https://forum.pritunl.com/u/thawthorn)\
**Post date:** [October 28, 2024, 11:25am UTC](https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549/1 "2024-10-28T11:25:31Z")

</div>

We run our Pritunl VPN server behind Cloudflare to protect the web UI. In the Pritunl config, our public IP is set to the real IP of our server (for the OpenVPN and Wireguard UDP traffic). The sync host is set to our full DNS hostname (Cloudflare). It worked great before our users updated to v1.3.4059.45. Now, all users experience a 40 second delay when connecting. Running tcpdump, the client now tries to connect to the public IP on port 443 and eventually times out. The user eventually can connect, but the long delay is not a great user experience.

I’m not sure for the reason for this change, but it doesn’t seem like whatever the client is trying to do is needed since the connection is eventually allowed.

Is there a setting we can set to avoid this behavior?

Thanks for any help.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [October 28, 2024, 4:02pm UTC](https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549/2 "2024-10-28T16:02:41Z")

</div>

When the connection code was rewritten the order was inadvertently changed from sorting sync remotes first to sorting profile remotes first. This will be fixed in an update possibly later tonight. Send the service logs from the top right menu to confirm it is only an issue with the remotes ordering.

---

<div class="post-metadata">

**Author:** ![thawthorn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/thawthorn/32/1023_2.png) [@thawthorn](https://forum.pritunl.com/u/thawthorn)\
**Post date:** [October 28, 2024, 4:26pm UTC](https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549/3 "2024-10-28T16:26:22Z")

</div>

Hi Zach,

Thanks for the help. Here you go (hostname and IP have been obfuscated to [vpn.host.com](http://vpn.host.com) and 1.2.3.4). [gist:0b95d8173ce9483e9adff6cd4eaead82 · GitHub](https://gist.github.com/thawthorn/0b95d8173ce9483e9adff6cd4eaead82)

(Too big to post here)

Thanks,

Trevor

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [October 28, 2024, 11:58pm UTC](https://forum.pritunl.com/t/new-connection-behavior-with-macos-client-v1-3-4059-45/2549/4 "2024-10-28T23:58:57Z")

</div>

This has been fixed in the codebase and will be included in the next release.