nginx

Terminate TLS and proxy traffic to upstream backends with nginx.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/MysticRyuujin/spirens --skill nginx-mysticryuujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nginx
Source: https://github.com/MysticRyuujin/spirens/tree/main/nginx
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill nginx-mysticryuujin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

nginx serves as a TLS-terminating reverse proxy for web3 infrastructure, but it does not handle ACME certificate issuance by itself. This Skill explains how to obtain certificates with certbot or equivalent tools and wire them into nginx configurations to securely terminate TLS and route traffic to backends.

Core Features & Use Cases

  • TLS termination and reverse proxy for web3 front-ends
  • HTTP/HTTPS routing with server_name and proxy_pass to upstream backends
  • TLS passthrough and mixed TLS scenarios for origin TLS inspection
  • DNS-01 wildcard certificate issuance and integration with certbot
  • Upstream load balancing, maps for conditional routing, and dynamic reconfiguration
  • Guidance for porting Traefik/Caddy setups to nginx

Quick Start

Install nginx, obtain certificates with certbot (DNS-01 for wildcards when needed), and configure a TLS-enabled server block that proxies to your backend service.

Frequently Asked Questions about nginx

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

FAQPage Schema
How do I configure nginx as a TLS-terminating reverse proxy for web3 infrastructure?

To configure nginx as a TLS-terminating reverse proxy, install nginx, obtain certificates with certbot, and set up a TLS-enabled server block that uses proxy_pass to route traffic to upstream backends. It enforces separate http and stream contexts.

Can I use certbot DNS-01 challenge to get wildcard certificates for nginx?

Yes, you can use certbot with the DNS-01 challenge to obtain wildcard certificates and wire them into your nginx configuration. This approach securely terminates TLS for multiple subdomains in web3 infrastructure setups.

Does nginx support TLS passthrough for mixed TLS scenarios alongside standard termination?

Yes, nginx supports TLS passthrough and mixed TLS scenarios for origin TLS inspection. It handles this by enforcing separate stream and http contexts, allowing dynamic certificate handling alongside standard HTTP routing.

What is the best way to handle certificate renewal and reload workflows in nginx?

The best way to handle certificate renewal is integrating certbot or equivalent ACME tools with nginx. After automatic renewal, trigger a careful certificate reload workflow to ensure the reverse proxy serves updated TLS certificates without downtime.

How do I port a Traefik or Caddy reverse proxy setup to nginx?

To port a Traefik or Caddy setup to nginx, translate your routing rules into nginx server_name and proxy_pass directives. You must manually configure certbot ACME integration and upstream load balancing, as nginx does not handle certificate issuance automatically.

Can I implement upstream load balancing and conditional routing with nginx?

Yes, you can implement upstream load balancing and conditional routing in nginx. It supports upstream blocks for backend distribution and maps for conditional routing, enabling dynamic reconfiguration of traffic across multiple web3 backends.