1.13.0-rc.0 #2019
Replies: 7 comments 5 replies
-
|
Are there already any plans for Android clients? |
Beta Was this translation helpful? Give feedback.
-
|
Yep! Android and iOS apps planned! Probably early next year.
|
Beta Was this translation helpful? Give feedback.
-
|
I just installed EE RC but am a bit lost. Where did OIDC setting page go? It used to be above “ sites” at the top of the sidebar but it’s nowhere to be seen? |
Beta Was this translation helpful? Give feedback.
-
|
Awesome release, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Is there a draft migration guide somewhere?
I'm unclear which of these are manual migration steps. It seems to me that I'd need to do something about my newt config for the 4th one above, but I don't presently have any clients so I'm unclear what I need to do. |
Beta Was this translation helpful? Give feedback.
-
|
As I was dealing with the You'd said that you were going to address that in the Issue I raised a week or two ago. Does this need a separate issue or...? I've addressed it I just wanted to mention it as a reminder. |
Beta Was this translation helpful? Give feedback.
-
|
Yep sorry will be fixed in the next release by the new
44470abd5457ba22b7cddf4fd434a2df79bfcdad
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
RC
A Release Candidate (RC) is a near-final software version, stable but undergoing last tests before official release. It has all features and no known bugs.
Warning
MIGRATIONS MAY BREAK BETWEEN RC VERSIONS
What's Changed
Breaking
Warning
This requires an update to Gerbil, Newt, Olm, and Pangolin.
Minimum Versions:
--accept-clientsflag from Newt; clients are on by default now with option to disable with--disable-clientsflag.enable_clientsfrom Pangolin configbranding.favicon_pathfrom private Pangolin config/app/public/favicon.icoin the containerbranding.login.title_textandbranding.signup.title_textfrom private Pangolin configNote
We've done our best to migrate Client Resources and Clients to the new Private Resources and Machine Clients. All pre-existing clients are now Machine Clients, and all Client Resources are now Private Resources. We've also attempted to migrate all pre-existing site associations to Private Resource access controls, and remote subnets to CIDR Private Resources. However, please review your configuration after updating to ensure everything has been migrated correctly.
Full Changelog: 1.12.3...1.13.0-rc.0
How to Update
Important
Always back up your config app-data before updating. This will allow you to easily roll back if the update breaks your configuration. You will not be able to easily downgrade otherwise.
View documentation
Private Resources, User Devices, and Machine Clients
Note
This is still in beta. We will work towards getting out of beta by early 2026.
This release introduces a major evolution of Pangolin’s networking model enabling a far greater suite of remote access technologies. This update transforms it into a fully self‑hosted, open‑source alternative to Twingate using WireGuard under the hood. You can now create a secure, seamless private network that connects users, machines, and multiple sites under one unified access layer.
Overview
With the new Private Resources, Machine Clients, and User Devices, Pangolin now enables private network access across distributed environments without traditional VPN complexity.
This effectively “flattens” your internal topology: once connected, resources across all sites are accessible without manually connecting to each individual site.
Private Resources
Private Resources represent network targets reachable through your site connectors. These can be defined at different granularities:
192.168.1.210).192.168.1.0/24).When a client connects to the Pangolin network, they can access these Private Resources using the same LAN addresses without any port forwarding, route table setup, DNS configuration, VPN configuration, or proxy redirection needed.
Each Private Resource also supports a “magic DNS” alias, allowing friendly hostnames like
mynas.internalto resolve automatically when connected. This simplifies navigation and behaves naturally across operating systems and clients.Fine‑grained access control allows admins to assign which users, roles, and machine clients can access each Private Resource.
Machine Clients
All existing “Clients” have now been migrated and renamed to Machine Clients.
Machine Clients are designed for servers, services, and automated systems (like CICD runners, monitoring, or backups) that need ongoing access to Private Resources.
They authenticate using familiar ID and secret credentials, and retain full compatibility with pre‑existing integrations while benefiting from the unified Private Resource model.
User Devices
User Devices bring private network access directly to end users. These authenticated clients connect securely through Pangolin and gain access to permitted Private Resources just like a corporate zero‑trust VPN.
This discussion was created from the release 1.13.0-rc.0.
Beta Was this translation helpful? Give feedback.
All reactions