>>Did you try to just have your nginx listen on port 80 and see if it works ? Yes, I did. It is not working. I need to whitelist my IP and for that I have to do some more paperwork. I'm in China. But my Chinese hosting company said I should use Socket (Socks?), but I don't know what they mean by that. My solution was to use another port (like port 81) and forward the traffic then. Any othby nginxn00b - Nginx Mailing List - English
>>First replace >>proxy_pass http://127.0.0.1:8080; >>by >>proxy_pass http://monsite.com:8080; Gee, so simple! Yes, that worked. Thank you very much!! To finish everything I need to forward port 81 to port 80. I guess a firewall rule will help me out here.by nginxn00b - Nginx Mailing List - English
>>Your backend / application isn't working that's why nginx can't connect to it and has to return 502. The app is up and running on port 8080. I can access the app directly using mysite.com:8080. Do I have to configure something else, maybe the firewall?by nginxn00b - Nginx Mailing List - English
Access control? Not that I know of. I didn't touch the firewall yet, so I guess there is none enable right now. >>curl -I http://localhost:8080 and see if you can connect. I did this on the server and I got: curl -I http://localhost:8080 curl: (7) couldn't connect to host And I tried from a remote client to connect via curl and got: curl -I http://myside.com:81 HTTP/1.1 502 Baby nginxn00b - Nginx Mailing List - English
Hi, I'm running nginx as a reverse proxy for a jetty. I host a Liftweb App on localhost:8080. Nginx is listening on Port 81. Here is my nginx.conf: server { listen 81; server_name mysite.com www.mysite.com; location / { proxy_pass http://127.0.0.1:8080; proxy_set_header X-Real-IP $remoby nginxn00b - Nginx Mailing List - English