原文网址Docker--解决nginx的502 Bad Gateway_IT利刃出鞘的博客-CSDN博客简介本文介绍如何解决Docker部署nginx做反向代理时出现502报错的问题。相关网址Docker--网络的配置-CSDN博客情景说明web程序和nginx都使用docker部署在Ubuntuweb程序是8090端口使用nginx做代理将请求转发到web程序web程序和nginx已经使用docker compose connect进行了网络连接nginx配置如下events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; server { # 所有IPV4的地址 listen 80; # 所有IPV6的地址 listen [::]:80; server_name 192.168.5.193; client_max_body_size 20m; charset utf-8; location / { proxy_set_header HOST $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://itthinktank; } } upstream itthinktank { server 127.0.0.1:8090; } }问题复现访问nginx时出现502页面原因分析docker与docker之间的通信是通过虚拟网桥docker0实现的需要使用docker0的ip表示本地网络不能使用127.0.0.1。解决方案使用docker0的ip。1.查看docker0的ip命令ifconfig2.将127.0.0.1改为docker0的ipevents { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; server { # 所有IPV4的地址 listen 80; # 所有IPV6的地址 listen [::]:80; server_name 192.168.5.193; client_max_body_size 20m; charset utf-8; location / { proxy_set_header HOST $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://itthinktank; } } upstream itthinktank { #server 127.0.0.1:8090; server 172.17.0.1:8090; } }