What's Changed
- Add geo-blocking to rules engine
- Add health checks to targets
- Add path-rewriting to targets
- Add refresh buttons to more tables
- Add header auth authentication method
- Improved targets input
- Cleaned up docs and readme
- BREAKING: Managed Pangolin Nodes are now Remote Nodes with a new container image (see below)
- BREAKING: Default Integration API port changed from
3004to3003- If you use the integration API, you will need to update the port in the Traefik dynamic config.
Full Changelog: 1.10.3...1.11.0
New Contributors
- @vmfventura made their first contribution in #1572
- @Shamilius made their first contribution in #1550
- @nicolaus-hee made their first contribution in #1588
- @iconoclasthero made their first contribution in #1608
- @OddMagnet made their first contribution in #1539
- @jln-brtn made their first contribution in #1522
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.
Managed -> Remote Nodes
In 1.9.0 we introduced Managed Pangolin Nodes which are self-hosted instances of Pangolin that are managed by our cloud control plane. Up until now, the main Pangolin container image could run as either a self-hosted instance or a Managed Node. This was too confusing and caused a lot of support issues.
Starting in 1.11.0, the main Pangolin container image (fosrl/pangolin) is only for self-hosted instances. Managed nodes are now called Remote Nodes and have their own container image (fosrl/pangolin-node). The code for remote nodes has been moved to its own repository: https://github.com/fosrl/pangolin-node.
Migration is very straightforward - just swap the container. Contact us via email or Discord if you need help.
services:
pangolin:
image: fosrl/pangolin-node:latest # It's best practice to pin to a specific version, e.g. pangolin-node:1.0.0
# ...License Update
Read the full post with details and more about how we arrived at this decision here: https://digpangolin.com/blog/posts/license-change
The high level:
The existing Pangolin Community Edition (CE) container (fosrl/pangolin) remains 100% AGPL‑3 compliant and fully open‑source – nothing has changed there.
We recently moved our SaaS (Cloud) code from a private downstream fork into the main repository to improve transparency and development speed. This cloud‑related code is licensed differently, as it powers our hosted service.
Additionally, we’re introducing a new Pangolin Enterprise Edition (EE), distributed separately under the Fossorial Commercial License (FCL). The EE container’s tag is prepended with ee. A few key things:
- It’s fully free for individuals (homelabbers, hobbyists, etc) and small businesses (under $100K annual revenue).
- The current EE build does not yet include enterprise‑specific features, but they’ll roll out soon. Right now, it’s identical to the CE.
- The CE remains the default. Using the EE is opt-in.
Read more in the documentation: https://docs.digpangolin.com/self-host/enterprise-edition
Our goal is to stay true to our open‑source principles, enable most of our large community to benefit from the full suite of features, and build a sustainable business that funds ongoing development.