Petio Docs
  • Introduction
  • FAQ
  • Install Guides
    • Docker
    • Linux
      • Debian 10/Ubuntu 20.04
      • Red Hat/Cent OS
      • Updating Petio
    • FreeBSD
    • MacOS
    • UnRAID
    • Windows
  • Configuration
    • First Time Setup
    • General Settings
    • Radarr
    • Sonarr
    • Console
    • User Profiles
    • Filters
    • Notifications
  • Reverse Proxy
    • Reverse Proxy Basics
    • Caddy
    • NGINX
    • Traefik (v2)
  • Troubleshooting
    • FAQ
  • Staff & Testers Only
    • Petio Pre-Release Workflow For Testers
Powered by GitBook
On this page
  1. Reverse Proxy

Reverse Proxy Basics

If you notice any mistakes that need to be corrected, please reach out on Discord!

PreviousNotificationsNextCaddy

Last updated 3 years ago

A good ELI5 explanation for a reverse proxy server is to think of it as a single point of entrance for your network as opposed to multiple points of entrance. It checks requests coming in through ports 80/443 - or whatever port you might specify differently - and directs those requests to the correct server such as Petio, Radarr or Sonarr. The reason why this is more secure is because rather than randomly punching holes in your firewall for each service, you are only forced to open up 1 or 2 ports that handle all the traffic.

We recommend you read on how to set up their SWAG container which contains all the necessary tools for a reverse proxy at home.

LinuxServer.io's guide