FlyingFish
FlyingFish on GitHub
  • FlyingFish
    • About the project
    • Screenshots
    • Installation
      • Quick Setup
      • Quick Update
      • Create Backup
      • Long setup
        • Env
        • Docker compose
          • Ports
          • Network
      • Storage management
      • FAQ
    • Configurations
      • Which user type am I
      • Listen
        • Port forwarding
        • Proxy protocol
        • IP Access
        • Gateway identifiers
        • UPnP Nat
      • Domains
        • DynDns Clients
        • Own DNS Server
        • Discussions Subdomains
        • DynDns Server
      • Routes
    • Examples
      • SSH hidden on HTTPS
      • FlyingFish to other reverse proxy
      • Backup Server, SSH to Nas
      • Own DynDNS Server - Fritzbox
      • Inventree - Route
    • Developer
      • Ideas, requests and bugs
      • Project structure
        • Under the hood
        • Service structure
        • Schema
        • Object name rules
      • Image build
      • Plugins
    • Contribution
Powered by GitBook
On this page
Edit on GitHub
  1. FlyingFish
  2. Configurations
  3. Listen

Proxy protocol

How is this to be understood?

PreviousPort forwardingNextIP Access

Last updated 1 year ago

As already mentioned in , a stream forwarded by Nginx cannot include the source IP. We help ourselves by activating the proxy protocol. As a result, the packet is taken and the information from the original IP is stored at the beginning.

As can be seen in the diagram, the stream still receives the original IP from the querying client. As soon as the stream connects to the reverse proxy, this is an internal connection with 127.0.0.1. The information is lost from the reverse proxy for the web server.

With the Proxy protocol, the reverse proxy receives the original IP with the package extension of the Proxy protocol header and can pass it on to the web server.

You can read more about it at .

Exploring the proxy protocol
Listen
Okay, a bit exaggerated ...