[Solved] Help centos6 nginx upstream cannot be forwarded to my own defined internal port

The reason is selinux problem. After closing it in /etc/selinux/config, restart it and it will be fine

• I created a redmine, and my host can access 192.168.33.55:3000 through the browser

• You can also access your own 192.168.33.55:3000 inside the virtual machine

• So I started to modify nginx to forward 8080 to port 3000 of the virtual machine

• But after nginx restarted, I accessed 8080 and received a 502 error

• But if I forward 8080 to nginx’s default 80, it’s ok

This is something wrong with me. Why can’t I forward to port 3000? Help

Reply content:

The reason is selinux problem. After closing it in /etc/selinux/config, restart it and it will be fine

• I created a redmine, and my host can access 192.168.33.55:3000 through the browser

• You can also access your own 192.168.33.55:3000 inside the virtual machine

• So I started to modify nginx to forward 8080 to port 3000 of the virtual machine

• But after nginx restarted, I accessed 8080 and received a 502 error

• But if I forward 8080 to nginx’s default 80, it’s ok

This is something wrong with me. Why can’t I forward to port 3000? Help

I guess that when you use curl to access: 3000, you use the root account, and when you use nginx to access: 3000, you may not use the root account. Judging from the log, when the tcp connection is permission denied, some online information says it is a problem with the SELinux configuration. You can check again according to this idea