1.9.4

What's Changed

• Fix/hostname field reset port and method by @Pallavikumarimdb in #1394
• Enhancement #906/Persist User Preference for Entries Amount by @Pallavikumarimdb in #1395

Full Changelog: 1.9.3...1.9.4

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

1.9.3

What's Changed

• Preserve subdomain input when selecting a base domain by @Pallavikumarimdb in #1375
• Enhancement #906/Smart Host Parsing for Target Address by @Pallavikumarimdb in #1316
• Feature #1318/Make version numbers link to GitHub releases and add Discord community link by @Hetav21 in #1387
• Support Unicode Domain Input and Display by @Pallavikumarimdb in #1240
• Various bug fixes and improvements by moi

New Contributors

• @Hetav21 made their first contribution in #1387

Full Changelog: 1.9.2...1.9.3

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

1.9.2

What's Changed

• Bug fixes for registering exit nodes
• Managed geoblocking

BREAKING

If you are on a managed node and update Gerbil to 1.2.1 you need to allow the proxy protocol with something like the following in your config/traefik_config.yml

websecure:
    proxyProtocol:
      trustedIPs:
        - 0.0.0.0/0
        - ::1/128

Full Changelog: 1.9.1...1.9.2

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

1.9.1

What's Changed

General bug fixes to integration API and migrations

New Contributors

• @SINF-KEN made their first contribution in #1341

Full Changelog: 1.9.0...1.9.1

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

1.9.0

What's Changed

• Add self-hosted managed mode to use the cloud for self-hosted highly available Pangolin
• Move site from resource to target so you can have multiple targets for a resource on different sites. This will allow you to create more highly available deployments!
• Auto redirect to IdP on a per-resource basis
• Setup token required to setup account for first time
• Fix domain picker to be more intuitive
• Breaking Change integration API to port 3004 by default
• General bugfixes and improvements

From the community!

• fix: adapt nix run command by @confusedalex in #1196
• Update versions by @Lokowitz in #1200
• System wide default language detection via browser language header by @Pallavikumarimdb in #1205
• Portbinding fixes by @Error-Gap in #1177
• make IPv6 optional during install by @Xentrice in #1212
• Added checks for port 80 and 443 by @aclfe in #1219
• Pangctl command to reset a user’s passkeys (WebAuthn credentials) by @adrianeastles in #1237
• Translation nb no by @EliasTors in #1242
• update node to LTS 22 by @Lokowitz in #1134
• fix: fixed api error message in createSite.ts by @jackrosenberg in #1262
• Update express to version 5 by @Lokowitz in #1246
• Add setup token security for initial server setup by @adrianeastles in #1208
• Form Signup Improvements - Password Requirements & Pre-Filled Email on signup form Invite by @adrianeastles in #1129
• add missing hostmeta export for PG schema by @Pallavikumarimdb in #1284
• fix: change default integration_api to 3004 by @jackrosenberg in #1281

Full Changelog: 1.8.0...1.9.0

New Contributors

• @confusedalex made their first contribution in #1196
• @Pallavikumarimdb made their first contribution in #1205
• @Error-Gap made their first contribution in #1177
• @aclfe made their first contribution in #1219
• @EliasTors made their first contribution in #1242

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

Managed Pangolin

In this deployment modality you can host your own nodes with cloud coordination and automatic fail over. Data always transits your servers and the cloud handles orchestration between all of your nodes.

It's essentially just the normal self hosted Pangolin setup, but with added benefits of cloud integration and coordinated fail over.

You can deploy a managed Pangolin node in seconds using the installer. Or you can convert your existing install

How It Works

• You Host the node: Run the same Pangolin stack as before with Traefik, which connects your Newt tunnels.
• We Handle the Rest: Pangolin Cloud manages the control plane, DNS, certificate management, database, and backups.

For detailed information about how nodes work and their advantages, see our nodes documentation.

Benefits

• High Availability: Eliminates the complexity of managing high availability while still owning your own infrastructure.
• Less Management Overhead: While we update the cloud with new features you don't need to touch your nodes unless you want to.
• Automatic updates The cloud dashboard evolves quickly, so you get new features and bug fixes without having to manually pull new containers every time.
• Cloud failover If your node goes down, your tunnels can temporarily fail over to our cloud points of presence until you bring it back online.

Managed deployment is ideal for organizations that need high availability while maintaining control over their infrastructure and data transit.

1.8.0

What's Changed

• Add client tunneling capabilities to Pangolin!
• Allow entering password even if security keys are present on an account
• Add basic member portal dashboard with links to visit resources
• Bug fixes related to resource domain create and update
• Clean up resources when deleting an org

Full Changelog: 1.7.3...1.8.0

New Contributors

• @ivenos made their first contribution in #1097
• @Xentrice made their first contribution in #1111
• @wayneyaoo made their first contribution in #1041
• @SigmaSquadron made their first contribution in #1138
• @jackrosenberg made their first contribution in #1104

How to Update

Important

For the clients to work you need to add port 21820 to the docker-compose.yml and update Gerbil. Please see a detailed guide here

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

Client tunneling

Introducing Pangolin Clients ("Olm")

We're excited to introduce Pangolin Clients (nicknamed "Olm") - a CLI-based peer-to-peer or relay VPN solution that transforms your Newt site into a secure connectivity hub without requiring open ports.

What are Pangolin Clients?

Pangolin Clients are a lightweight VPN solution built on a hub-and-spoke model:

• Your Newt site acts as the hub, with clients as the spokes
• Unlike mesh-based systems (Tailscale, NetBird), this centralized approach provides VPN capabilities without opening ports
• Data relays through Gerbil on your VPS, with optional --holepunch for direct NAT hole-punching connections

Key Features

Cross-Platform Support: CLI clients available for macOS, Windows, and Linux

Flexible Access Control:

• Grant clients access to one or more sites (requires --accept-clients flag in Newt)
• Control specific network resources or allow full network access
• Define clients with secret credentials (similar to defining sites in Pangolin)

Secure Connectivity: Leverages the same port-free security model as Newt's browser-based access

Use Cases

• Multi-network connectivity: Connect home, office, and cloud VPCs
• Remote management: Use Newt as a jump box for SSH and other remote access
• Lightweight VPN alternative: Secure connectivity without complex mesh configurations
• Self-hosted remote access: Maintain control over your VPN infrastructure

Current Status

This is an early-stage release designed to gather community feedback. The clients are currently minimal and CLI-only, not yet tied to user accounts. We're releasing this basic version to see if the community finds it useful - if so, we'll continue to refine and expand the feature set!

Getting Started

Ready to try Pangolin Clients? Update to version 1.8.0 and follow our migration guide to update all components.

Resources:

• Client demo video
• Migration guide

We're excited to see how you use this new capability and welcome your feedback as we continue building the best self-hosted remote access solution!

1.7.3

What's Changed

• Allow SMTP without authentication credentials
• Fix bug causing redirect on OIDC log in if flags.disabled_user_create_org is enabled
• Allow multi-level subdomain inputs in domain picker
• Improve external user create wizard

Full Changelog: 1.7.2...1.7.3

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

1.7.2

What's Changed

• Add traefik.cert_resolver and traefik.prefer_wildcard_cert config options for domains created via the GUI

Full Changelog: 1.7.1...1.7.2

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

1.7.1

What's Changed

• Fix exit node ping bug with Newt
• Fix bug causing resources on local sites to go to 404

Full Changelog: 1.7.0...1.7.1

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

1.7.0

What's Changed

• Add passwordless log in via passkeys
• Add option to enforce 2fa on a user from the Server Admin panel
• Add option to add domains to organizations via the UI
• Add refresh button to sites
• Display last known Newt version in sites table with notification to update if out of date
• Remember last visited organization when visiting dashboard
• Visual styling improvements to the UI and sidebar
• Add stricter rate limits to auth endpoints

Full Changelog: 1.6.2...1.7.0

New Contributors

• @Burzhui34 made their first contribution in #1023
• @daeho-ro made their first contribution in #1054
• @jnewing made their first contribution in #1035
• @adrianeastles made their first contribution in #1011

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

Passkeys Support

You can now set up and manage security keys to log in without a password. Thanks to @adrianeastles for leading this effort!

Host Your Own Highly Available Pangolin Node

We're excited to announce the early stages of Pangolin Cloud (beta), a fully managed and highly available solution for exposing your resources. Currently, our points of presence (exit nodes) are located in the US, with plans to expand to the EU in the very near future. As part of this offering, we're developing a new feature that allows you to host your own point of presence on the infrastructure of your choice, with seamless failover to Pangolin Cloud. This ensures that data flows through your servers while we handle high availability failover during downtime. Here’s how it works:

• You Host the Exit Node: You manage the infrastructure for your exit node, which connects your Newt tunnels.
• We Handle the Rest: Pangolin Cloud manages the control plane, DNS, certificate management, database, and backups.
• Failover Made Simple: You can host multiple exit nodes, and we’ll coordinate failover between them. If none of your nodes are available, traffic will automatically fail over to our cloud nodes.

This hybrid approach gives you control over your data flow while eliminating the complexity of managing high availability.

If you're interested in this self-hosted exit node model, please send us an email at numbat@fossorial.io. Let us know a little bit about yourself, your intended use cases, and any questions or concerns, and we'll get back to you!

You can already sign up and try the fully hosted version of Pangolin: https://pangolin.fossorial.io/auth/signup