reverse-proxy

Expose internal NetBird services via HTTPS with authentication and custom domains.

Updated Mar 6, 2026

Search Tags:#authentication #custom domain #reverse proxy #tls #https #netbird #expose service

Ready to run

npx skills add https://github.com/renne/skills --skill reverse-proxy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-proxy
Source: https://github.com/renne/skills/tree/main/netbird/reverse-proxy
Command: npx skills add https://github.com/renne/skills --skill reverse-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows you to securely expose internal services running on your NetBird network to the public internet without the need to open firewall ports or configure complex network setups.

Core Features & Use Cases

Secure Public Access: Make internal applications accessible via HTTPS without exposing your internal network.
Flexible Targeting: Route traffic to specific peers, hosts, domains, or subnets within your NetBird network.
Authentication: Protect exposed services with SSO, password, or PIN code authentication.
Custom Domains & TLS: Use your own domains with automatic TLS certificate management (ACME) or static certificates.
Use Case: You have a self-hosted Home Assistant instance that you want to access securely from outside your home network. This Skill can configure NetBird to provide a public HTTPS URL for it, complete with authentication.

Quick Start

Use the reverse-proxy skill to expose the service running on peer 'my-nas' on port 8080 using the custom domain 'nas.example.com'.

Frequently Asked Questions about reverse-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I expose internal services to the public internet without opening firewall ports?▼

A NetBird reverse proxy enables secure external access to internal services without opening firewall ports. It manages service exposure, target routing, domain configuration, and authentication methods like SSO, passwords, and PIN codes.

Can I use a custom domain with automatic TLS certificates for my self-hosted applications?▼

Yes, custom domains are supported with automatic TLS certificate management via ACME or static certificates. This ensures secure HTTPS connections for your self-hosted applications exposed through the reverse proxy.

Does NetBird reverse proxy support SSO and password authentication for exposed services?▼

Yes, the reverse proxy supports SSO, password, and PIN code authentication to protect exposed services. This ensures that internal applications remain secure when accessed from the public internet.

What is the best way to route traffic to specific peers or subnets within a NetBird network?▼

The best way to route traffic to specific peers, hosts, domains, or subnets within a NetBird network is by configuring target routing in the reverse proxy. It also supports path-based routing and trusted proxy configurations for backend applications.

Do I need to configure complex network setups to make internal applications accessible via HTTPS?▼

No, you do not need complex network setups to make internal applications accessible via HTTPS. The reverse proxy handles secure public access without requiring you to open firewall ports or configure complex networking rules.