Pangolin 1.27 is here, and most of it is about the clients. The headline feature is managed client settings: admins can now set connection settings for every user in a role from the dashboard. Every client also gets per-organization settings, so connection settings switch when you switch organizations. On top of that, the Mac and iOS apps now show logs right in the app.
Release Highlights
Managed Client Settings
Until now, every user configured the Pangolin client on their own device. If you wanted a team to use a particular DNS server, always route through an exit node, or use a specific MTU, you had to walk each person through the settings or push a pangolin.json to every machine via an MDM solution. Managed client settings move that into the dashboard. You set the values once on a role, and every user in that role gets them the next time their client connects.
Open Team → Roles, pick a role, and go to the Client Settings tab. Turn on Manage Settings from Role, then edit the groups you want to control:
- DNS: Enable Aliases (DNS Override), DNS Over Tunnel, primary and secondary upstream DNS servers, and match domains.
- Exit Node: the gateway resource that carries client traffic, and whether the exit node takes precedence over resources.
- Advanced: MTU and Prefer Local Routes.
1 / 4
You don't have to manage everything. Every setting can be left as Set by client, so you only take over the settings you care about and leave the rest to the user. On/off settings can be forced On or Off, and text and number fields are left to the client when they're blank.
On the client, managed settings show up under Settings → Connection. A banner tells the user how many settings their administrator manages, and each managed setting has a lock next to it and can't be changed on the device. A managed value overrides the user's own choice, organization-level settings, and any pangolin.json on the device, including system-wide config files.
If a user has more than one role, settings are never merged across roles. They get the settings of the oldest role that manages client settings. The simplest setup is a dedicated role that only manages client settings, with the option left off on every other role.
Managed client settings work on Mac, iOS, Windows, Linux, and Android. They are available on the Business plan and above in Pangolin Cloud and in self-hosted Enterprise Edition. See the server-side client settings docs.
Per-Organization Settings in All Clients
Client settings are now split into two pages: General and Connection. General covers app behavior like starting at login and updates, which are the same no matter which organization you're in. Connection covers DNS and routing: aliases, DNS over tunnel, upstream DNS servers, match domains, exit node precedence, and MTU.
Connection settings can now be set per organization. By default, every organization uses your settings for all organizations. Pick Use Own Settings on an organization to give it its own copy. From then on, changes only apply to that organization, and when you switch organizations the client switches its connection settings with you. Reset puts the organization back on your shared settings.
This is useful for anyone who belongs to more than one organization. Some examples:
- Different DNS servers per org. Your company org can resolve through an internal DNS server reached over the tunnel, while your homelab org uses Pi-hole on your home network.
- Different match domains. Send
*.corp.example.comupstream in one org and*.home.arpain another, without editing the list every time you switch. - Different routing. Turn on exit node precedence in an org where all traffic should go through a gateway, and leave it off in an org where you only want access to a few resources.
- MSPs and consultants. Keep a separate DNS and routing setup for each customer org and switch between them in one click.
Managed client settings stack on top of this. If an admin manages a setting for your role in an organization, it applies in that organization no matter what you've set locally.
Per-organization settings are available in the Mac, iOS, Windows, Linux, and Android apps. See connection settings.
Logs in the Mac and iOS Apps
Troubleshooting the Mac client used to mean opening Console.app, filtering for the right process, and digging through system logs. On iPhone and iPad, it was harder still. Now the logs are built into the app. Open About to tail the client's logs live, with a timestamp, level, and message for each line.
You can Clear the view to start fresh before reproducing a problem, and Save the logs to a file to attach to a support request or GitHub issue. See the Mac and iOS client docs.
Other Small Updates
- Custom CSS for custom branding. Self-hosted Enterprise Edition can now add your own stylesheet to authentication pages. Set
auth_page_custom_cssunderbrandinginprivateConfig.ymlto style every auth page on the server, including the dashboard login, signup, password reset, organization login, and resource authentication pages. You can also add Custom CSS in an organization's branding settings in the dashboard, which applies to that organization's login and resource authentication pages. See custom branding.
General Improvements and Bug Fixes
As always, this release also includes various UI improvements and bug fixes throughout the product.
Get notified of new releases
Follow the release feed in any RSS reader to see each new Pangolin release as soon as it is published.
About Pangolin
Pangolin is the open-source access platform that lets IT and security teams connect their workforce, AI agents, and infrastructure without the friction of legacy VPNs and stitched-together security tools. By unifying a zero-trust VPN, zero-trust reverse proxy, privileged access management, and an identity-aware AI gateway under one policy model, Pangolin helps organizations shrink their attack surface, contain stolen credentials, and pass audits with less work. Teams can roll it out one service at a time, self-hosted or on Pangolin Cloud, and verify exactly how their access is secured because every component is open source.
