n8n-nodes-gluetun
v0.1.5
Published
n8n community node to control a gluetun VPN client via its HTTP control server
Maintainers
Readme
n8n-nodes-gluetun
Community node for n8n to control a gluetun VPN client through its HTTP control server.
✅ Verified community node — available directly from the node panel in n8n (self-hosted and n8n Cloud).
Installation
This is a verified community node: in n8n, click + (Add node) and search for
gluetun — no manual install needed.
Settings → Community Nodes → Install → n8n-nodes-gluetun.
Operations
| Operation | Endpoint | Description |
|---|---|---|
| Get Public IP | GET /v1/publicip/ip | Public IP, country, region of the VPN exit |
| Get VPN Status | GET /v1/vpn/status | Current VPN status (running / stopped) |
| Set VPN Status | PUT /v1/vpn/status | Start or stop the VPN |
| Get Forwarded Port | GET /v1/openvpn/portforwarded | The VPN forwarded port |
| Get DNS Status | GET /v1/dns/status | Current DNS-over-TLS status |
Credentials
Create a Gluetun API credential:
- Base URL — e.g.
http://gluetun:8000(control server address;HTTP_CONTROL_SERVER_ADDRESS). - API Key — only if the control server has API key auth enabled (sent as
X-API-Key).
Example
Keep your torrent client in sync with the VPN: Get Forwarded Port → push the value into your download client's listening port. Or Get Public IP on a schedule and alert if the VPN exit changes or drops.
Build
npm install --ignore-scripts
npm run buildUsage example
Read the VPN public IP:
- Add the node after a trigger (e.g. When clicking 'Test workflow').
- Select your credential.
- Get Public IP.
- Execute the node — example output:
{ "public_ip": "146.70.194.87", "country": "France", "city": "Paris" }Disclaimer
This project isn't affiliated with or endorsed by the gluetun project. gluetun is the property of its respective authors.
