1.19.0

[oschwartz10612]

Read the 1.19 Announcement

Read the full announcement with discussion of new features: Pangolin 1.19: Browser Remote Access — SSH, RDP, VNC & More

What's Changed

• Add resource policies for public resources
• Add browser based RDP access via public resources (requires newt >1.13.0)
• Add browser based VNC access via public resources (requires newt >1.13.0)
• Add browser based SSH access via public resources (requires newt >1.13.0)
• Add native Pangolin SSH mode (for private and public resources) that does not require configuring OpenSSH server and PAM (requires newt >1.13.0)
• Add auto update Newt option for all sites in the org or specific sites (requires newt >1.13.0)
• Add searchable and filterable custom labels on sites and resources
• Add share link post authentication redirect path
• Add pangctl command to make more than one user server admin
• Add PostgreSQL and Redis install options in the installer
• Fix public resource showing as degraded when WireGuard targets were added alongside healthy Newt targets
• Fix custom branding logo URL not accepting links
• Fix pasting the device code not accepting paste
• Fix enforce absolute paths in sudo commands
• Fix refresh end time on logs tables
• Fix accept partially valid Docker labels instead of rejecting all
• Fix restarting container on RC version causing migration errors
• Fix cross site target assignment
• Improve OpenAPI response payloads
• Improve SSH configuration on private resources
• Improve sort resource filter options in audit logs
• Improve performance in certain hot paths
• Improve clients get error when holepunching fails instead of getting stuck registering
• Improve speed of API endpoints with thousands of sites and users
• Improve add loading icons on all logs tables
• Improve auto create roles added in Blueprints
• Dependency security updates
• General UI improvements
• Various other bug fixes

How to Update

Important

1.19.0 browser-based SSH requires the Badger Traefik plugin to be on the latest version v1.4.1. The migration will automatically do this if it can find the Traefik config in the standard location. Otherwise, please ensure your Badger is up to date.

Important

Browser-based RDP, SSH, and VNC as well as the new Pangolin SSH mode requires Newt version 1.13.0 or greater.

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

---

This discussion was created from the release 1.19.0.

[Blacks-Army]

Why were all versions re-released? Has something been compromised?

[oschwartz10612]

No it was a mistake unfortunately the tags got deleted and we had to relink all of the releases to the right tag.

[wallacebrf]

Love the SSH and VNC support they is awesome

[durango99]

Will there be audio redirection with the new 1.19 RDP web client?

[oschwartz10612]

I am not sure if it currently supports it but we could work this in to make sure it can.

[yann117]

@oschwartz10612
I have a homelab at home, with my own domain. I run Pangolin and other services (Immich, Jellyfin, ...) using Docker.
I don't have Newt on that homelab, all my resources are public resources, defined in the local node.

Now, I tried to use the SSH connectivity, defining a new public resource, selecting Pangolin SSH, then I can select my local site as the destination node.

However, then I cannot use that resource to connect as SSH to my local node/homelab:

• the connection in the browser session ends in HTTP 503/Service Unavailable
• setting DEBUG log, show nothing specific in pangolin

I see in the documentation, that running Newt for Pangolin SSH is required ... but that doesn't make a sense for a local node.
If this scenario is not supported, why are we able to select a local node in the destination target?

[ToBinio]

Hi, I would like to advocate for labels to become a CE feature.

I believe having basic organization falls under "core functionality."
Personally, I share a home server with a friend, and it would be great to be able to label which side project belongs to whom.

Thanks for your consideration!