Linux Labs· Linux Server ServicesLab 21 of 26

Nginx Reverse Proxy in Front of a Private Application

The application lives on server2 and only the edge may talk to it. Put nginx on server1 in front of it under a public name, forward the headers the app needs, bound the timeouts, let SELinux allow exactly that, then take the backend away and watch the proxy recover on its own.

  • Intermediate
  • 50 min
  • Not rated yet
Start labPart of Advanced Linux System Administration
  • A real environment in your browser
  • You run the commands yourself
  • Your result is checked automatically

In this moduleLinux Server Services

  1. BIND Authoritative Forward and Reverse DNS55 min
  2. Restricted DNS Caching and Forwarding45 min
  3. Secondary DNS and Authenticated Zone Transfer55 min
  4. Apache Name-Based Virtual Hosts50 min
  5. Nginx Reverse Proxy in Front of a Private ApplicationYou are here
  6. Apache HTTPS with a Training CA55 min
  7. Rotate the Certificate on an HTTPS Reverse Proxy55 min
  8. Samba Authenticated Team Share50 min
  9. MariaDB Administration and Least-Privilege Access55 min
  10. Postfix Local Notifications and the Mail Queue45 min