Published October 3, 2025 | https://doi.org/10.59348/hqabg-q5h89

Pangolin, Newt, Gerbil and custom ports

Creators & Contributors

  • 1. Birkbeck, University of London, English and Humanities

I have been playing around with Pangolin, a really nice management system for exposing internal services over HTTPS.

However, I found that its internal wireguard networking does not play nicely if you already have another wireguard system, like tailscale, on the box. The solution was actually simple, but has a potential tripwire.

In your docker-compose.yml, set something like this under Gerbil's ports:

- 51821:51821/udp

However, importantly: these ports must MATCH. You cannot have "- 51821:51820/udp" or similar. This will cause the Newt tunnels to fail.

Then, in pangolin/config/config.yml, make sure that the Gerbil port is set to 51821 or whatever your selected port is. Tada.

Pangolin, Newt, Gerbil and custom ports was originally published by Martin Paul Eve at eve.gd: Martin Paul Eve on October 04, 2025.

Files

10.59348_hqabg-q5h89.pdf

Files (104.7 kB)

Name Size Download all
md5:516f337e69f53ed719c7777d1e50d768
104.7 kB Preview Download

Additional details

Description

I have been playing around with Pangolin, a really nice management system for exposing internal services over HTTPS. However, I found that its internal wireguard networking does not play nicely if you already have another wireguard system, like tailscale, on the box. The solution was actually simple, but has a potential tripwire.

Identifiers

GUID
https://doi.org/10.59348/hqabg-q5h89
URL
https://eve.gd/2025/10/04/pangolin-newt-gerbil-and-custom-ports/

Dates

Issued
2025-10-03T23:00:00Z
Updated
2025-10-03T23:00:00Z