June 2024
Beginner to intermediate
268 pages
6h 26m
English
The output from curl suggests that requests seem to be working fine. But to avoid forcing your users to pass high-numbered ports around with your chosen domain, like webrtc.example.com:3000, it’s time to put Nginx to work as a reverse proxy.
Historically, web proxies work on the user’s side, taking a web request and passing it along to a standard port on another web server. Nginx functions as a “reverse” proxy because it moves in the opposite direction on the server’s side. That is, a reverse proxy processes requests coming in over HTTPS/port 443 on your domain and routes them on your server to a private address like localhost:3000.
Open up your per-domain configuration file inside of /etc/nginx/conf.d/ ...
Read now
Unlock full access