🎉 Outline Client 1.16.0 Released

[jyyi1]

We're excited to announce the release of Outline Client version 1.16.0!

This update includes the following changes:

• Introducing "Dark Theme": you can switch themes via the "Appearance" menu now: Dark theme #1366
• Fixed an issue that would sometimes show a "failed to connect" false alert: Failure to read salt on certain mobile networks #2561
• General bug fixes and usability enhancements

Thank you to everyone who contributed to this release, especially to the following users for their excellent contributions:

• feat(client): add dark mode #2461 by @Kief5555
• refactor(client): use client when creating a new tunnel #2498 by @emohandesi
• fix(client): enhance link visibility in dark mode #2543 by @Kief5555
• feat(client): support connecting/disconnecting from status bar for macOS #2523 by @Kief5555

Linux and Windows users can update to the new version today. Android, iOS, and macOS users will receive the update over the next several days.

[romeozzzzz]

awesome news gyus! waiting for IOS/MacOS updates with no patience

[khantzawhein]

#2576

Please take a look at this issue before pushing updates to larger platforms. This issue prevents users from using Prefix Disguise feature. @jyyi1 @fortuna @daniellacosse

[jyyi1]

We're temporarily paused the release to fix the issue mentioned above (#2576 ). Please expect some delays.

If you are experiencing this issue, please install the previous version: Windows 1.15.1, Linux 1.15.1. We've disabled auto-updates, so it won't automatically update to the new, problematic release.

[Kief5555]

@jyyi1 Do you know if the Outline Team will be producing a new .16.1 release that addresses the merged PR(s)? #2579 #2572

Cheers!

[jyyi1]

Yes, we've sent the hotfix version to our QA team.

[SadeghSalman]

Is there any update about new release?

[jyyi1]

Hello everyone,

🎉 We've just released Outline Client 1.16.1 for Linux and Windows. 🎉

Please try the new version and let us know if the issues you've been discussing have been fully resolved.

The Android and iOS/macOS versions will be pushed to your devices in the coming days.

Thanks again for your patience and support!

[SadeghSalman]

Tested with Windows 11
Version 24H2
5G Router || 4G mobile hotspot || Fiber Optic Router
All passed.

[alexander-potemkin]

Ubuntu 24.04 LTS seems to be working fine (except for the crash with WebSocket, which is handled separately).

[SadeghSalman]

Hello Jigsaw Team.

Is there any new version for android and iOS ?

[jyyi1]

Yes, new versions are awaiting review from Google and Apple and will be rolled out over the next seven days.

[khantzawhein]

Hello Jigsaw Team,

I found a new issue on Outline 1.16.1 again. Please check it out.

#2588

While this issue doesn't prevent the user from establishing the connection, it takes really long to connect VPN if UDP is blocked in the user's network.

[khantzawhein]

@jyyi1 @fortuna, please, before rolling out to Android and Apple, kindly take a look into it.

As a server provider, I will run into a lot of user complaints if this is rolled out to iOS and Android.

[jyyi1]

Thanks for bringing this to our attention.

You are absolutely right. The PR you mentioned does increase the UDP connection check time. We can reduce the retries to 3, which will shorten the total timeout to be 15 seconds.

But it won't be included in this release. We're still rolling out 1.16.1 because fixing the inability to connect is more urgent. In the meantime, you might want to inform your users that the initial connection might take a little longer.

[khantzawhein]

I think 2 seconds with 3 retries should be enough because no server can have a round-trip latency time of 2000ms, unless that server is really overloaded or the client got a really bad connection.

[khantzawhein]

UDP blocking is somewhat common in my country because most VPN connections are on UDP.
They block UDP on any grey IP that they suspect is a proxy.

So shortening the timeout on UDP and faster fallback to TCP would definitely help.

[jyyi1]

The ideal solution would be to not pre-test UDP at all. Instead, we'd dynamically monitor DNS traffic during the connection. If DNS server fails to respond within a specific time, we could automatically switch to TCP (or a more secure DNS protocol like DoT or DoH) and remember the decision.

However, this change would require more code modifications and a longer development cycle. We'll certainly consider this for future updates.

[alexander-potemkin]

latest stable iOS, updated to the latest version of Outline and got error:

SessionConfigFetchFailed: failed to fetch the URL
Details: {
  "url": "https://DNS/URL"
}
Cause:   ERR_INTERNAL_ERROR: Get "https://DNS/URL": dial tcp IP:443: connect: no route to host

And the app got in a dead loop of connecting and disconnecting. I'm not 100% sure, but probably, during the installation the VPN has been active.

Only managed to solve that by removing VPN profile from the settings and reinstalling.

From what I understand, there has been no changes that could provoke such a behavior? (yet here it is and I've also heard about some other connections failures, but don't have the details yet and it self healed somehow)

[jyyi1]

Thanks for reporting the error. We've seen a few similar issues related to Apple's VPN API, but we're still not sure about the root cause (maybe Apple is not able to handle VPN profiles from multiple app versions?).

And yes, removing VPN profile and reinstalling is the best way to fix this for now.

[alexander-potemkin]

Thanks for confirming and letting me know. It's the first time I'm observing that kind of behavior, even thought I'm using VPNs in various degrees, including on iOS for ~10 years.

Maybe other apps are doing something different?

I know that I might be repeating that too often, but WireGuard was and is the most stable product I've ever used. Mentioning that just in case if something could be borrowed from there.