Hey guys, what is the common practice for chaining two reverse proxies together? I have an instance of Nginx Proxy Manager (i.e., npm) setup on my local network and a public IP pointed to that to access internal services.

Recently I stood up a VPS with an instance of npm running to attempt to get around my work firewall from blocking my internal services and it seems to work. That said, how do I:

  1. Point the external reverse proxy to my internal proxy/ip?

For my domain, I imagine I would point the dns to the external VPS, allow 80/443 and point to my private IP. Is this the correct way to set this up?

References:

- VPS as gateway

- Use VPS as reverse proxy

  • zfa@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    You can either point the first proxy to the second proxy, or point it to the backends directly. Depends if you have firewalls in the way that stop the VPS proxy reaching your backends directly; or if that internal nginx instance is dong anything clever like handling auth, adding headers etc. etc.

    In your instance I’d more likely have the VPS locked down and unable to access my internal resources and just open up its access to my internal nginx instance. Therefore chaining proxies would be my approach but there’s no right or wrong.