If you are able, please report issues or feature requests via GitHub; support will still be provided here but GitHub is the preferred method. https://github.com/Joly0/unraid-pangolin_cli/issues

Pangolin CLI

An Unraid plugin that installs the Pangolin CLI and adds a settings page to connect your server to a Pangolin instance as a machine client. This lets you reach private resources directly on your Unraid host.

From Pangolin themselves:

A client is a way to access resources on sites remotely and privately via a virtual private network. Clients are used with private resources to faciliate zero-trust network access.

https://docs.pangolin.net/manage/clients/understanding-clients

Installation

Community Application

Install via the Community Applications plugin in unRAID by going to the 'Apps' tab and searching for 'Pangolin CLI'.

Manual Install

Install manually by navigating to:

Plugins → Install Plugin and entering the plugin URL:

https://github.com/Joly0/unraid-pangolin_cli/raw/main/pangolin_cli.plg

Edited July 12Jul 12 by Joly0

Reserved

Reserved

Reserved

Thank you for this! :)

For some reason I'm experiencing problems with the dns resolution: Immediately after connecting the CLI it works great but when my backups run at night they're unable to resolve the internal dns - unraid seems to lose it after some time.

I'm running this alongside with Tailscale but according to the description on "override system dns" this shouldn't be a problem. Here's the logs - the disconnect was not triggered manually - any idea what could be going on here / where I could start looking?

INFO: 2026/09/30 11:57:46 WireGuard connection to site 7 is CONNECTED (RTT: 16.456231ms)
2026-09-30 12:07:06 ==== Pangolin client disconnecting ====
INFO: 2026/09/30 12:07:06 Received exit request via API
INFO: 2026/09/30 12:07:06 Tunnel process context cancelled, cleaning up
Received shutdown signal, stopping tunnel
INFO: 2026/09/30 12:07:06 Restoring original DNS configuration
INFO: 2026/09/30 12:07:06 DNS configuration restored successfully
INFO: 2026/09/30 12:07:06 Hole punch manager stopped
INFO: 2026/09/30 12:07:06 Stopped holepunch connection monitor
INFO: 2026/09/30 12:07:06 UDP hole punch goroutine ended for all exit nodes
INFO: 2026/09/30 12:07:06 Processing shutdown request via API
INFO: 2026/09/30 12:07:06 Restoring original DNS configuration
ERROR: 2026/09/30 12:07:06 Failed to restore DNS: failed to restore DNS: no backup file exists
INFO: 2026/09/30 12:07:07 DNS proxy stopped
INFO: 2026/09/30 12:07:07 DNS proxy stopped
INFO: 2026/09/30 12:07:07 Released shared UDP bind
INFO: 2026/09/30 12:07:07 Olm service stopped

On 10/1/2026 at 12:04 PM, Luvide said:

Thank you for this! :)

For some reason I'm experiencing problems with the dns resolution: Immediately after connecting the CLI it works great but when my backups run at night they're unable to resolve the internal dns - unraid seems to lose it after some time.

I'm running this alongside with Tailscale but according to the description on "override system dns" this shouldn't be a problem. Here's the logs - the disconnect was not triggered manually - any idea what could be going on here / where I could start looking?

INFO: 2026/09/30 11:57:46 WireGuard connection to site 7 is CONNECTED (RTT: 16.456231ms)
2026-09-30 12:07:06 ==== Pangolin client disconnecting ====
INFO: 2026/09/30 12:07:06 Received exit request via API
INFO: 2026/09/30 12:07:06 Tunnel process context cancelled, cleaning up
Received shutdown signal, stopping tunnel
INFO: 2026/09/30 12:07:06 Restoring original DNS configuration
INFO: 2026/09/30 12:07:06 DNS configuration restored successfully
INFO: 2026/09/30 12:07:06 Hole punch manager stopped
INFO: 2026/09/30 12:07:06 Stopped holepunch connection monitor
INFO: 2026/09/30 12:07:06 UDP hole punch goroutine ended for all exit nodes
INFO: 2026/09/30 12:07:06 Processing shutdown request via API
INFO: 2026/09/30 12:07:06 Restoring original DNS configuration
ERROR: 2026/09/30 12:07:06 Failed to restore DNS: failed to restore DNS: no backup file exists
INFO: 2026/09/30 12:07:07 DNS proxy stopped
INFO: 2026/09/30 12:07:07 DNS proxy stopped
INFO: 2026/09/30 12:07:07 Released shared UDP bind
INFO: 2026/09/30 12:07:07 Olm service stopped

Hey, sorry for the late reply.

So this doesnt seem like a direct issue with the plugin itself. The problem seems to be, that pangolin changes unraids resolv.conf file for its dns resolving without letting unraid know it (there is basically no way for me to properly implement this properly unfortunately). It can happen, that when unraid does changes to the resolv.conf file when pangolin cli is up and connected then the original unraid file is restored and the changes from pangolin are reverted. This can for example happen when the server uses DHCP and the DHCP lease is renewed or when tailscale settings change and tailscale writes changes to the resolv.conf file.

If this happens again, can you please run these commands:

cat /etc/resolv.conf
pangolin status client --json
iptables -S INPUT | grep -n -e pangolin -e ts-input
tail -50 /var/log/pangolin_cli.log

and please post the results either here or better create an issue on my github https://github.com/Joly0/unraid-pangolin_cli