nginx docker connect()在连接到上游时失败(110:连接超时),相同的配置在没有docker的情况下工作,可能有什么问题?
我有一个来自nginx docker image的反向代理nginx docker connect()在连接到上游时失败(110:连接超时),相同的配置在没有docker的情况下工作,可能有什么问题?,docker,nginx,kubernetes,nginx-reverse-proxy,amazon-eks,Docker,Nginx,Kubernetes,Nginx Reverse Proxy,Amazon Eks,我有一个来自nginx docker image的反向代理nginx:stable Dockerfile: FROM nginx:stable COPY main.conf /etc/nginx/conf.d/default.conf COPY nginx.conf /etc/nginx/nginx.conf COPY liveness /liveness RUN chmod +x liveness/liveness_probe.sh 反向代理有时会随机返回502个坏网关,我可以在日志
nginx:stable
Dockerfile:
FROM nginx:stable
COPY main.conf /etc/nginx/conf.d/default.conf
COPY nginx.conf /etc/nginx/nginx.conf
COPY liveness /liveness
RUN chmod +x liveness/liveness_probe.sh
反向代理有时会随机返回502个坏网关,我可以在日志中看到:
2020/09/30 10:51:07 [error] 28#28: *67 connect() failed (110: Connection timed out) while connecting to upstream, client: xx.xx.xx.xx, server: , request: "POST xx HTTP/1.1", upstream: "xx", host: "xx"
main.conf:
server {
listen 80;
listen [::]:80;
#Seconds to wait for timeout
# fastcgi_read_timeout 300s;
proxy_buffers 32 4m;
proxy_busy_buffers_size 25m;
proxy_buffer_size 512k;
proxy_ignore_headers "Cache-Control" "Expires";
proxy_max_temp_file_size 0;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Connection "";
client_max_body_size 1024m;
client_body_buffer_size 4m;
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;
proxy_intercept_errors off;
proxy_http_version 1.1;
location ^~ / {
proxy_pass https://xx.com;
}
}
nginx.conf:
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 2048;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/conf.d/*.conf;
}
真正奇怪的是,如果我在带有ubuntu 20.04的vm中使用相同的配置并安装nginx包(不带docker),反向代理可以正常工作,而不会出现随机的110连接错误
这里可能出了什么问题
一切都在aws-eks的alb入口控制器后面
为了丢弃入口控制器问题,我还公开了负载平衡器服务,问题仍然存在,因此丢弃了所有alb入口控制器问题
更新:
好的,我刚才做的另一个测试是在反向代理工作的同一个虚拟机中进行docker构建和docker运行,将它绑定到另一个端口,它不会返回502,似乎docker容器调度所在的集成节点有问题。nginx容器无法访问
https://xx.com
有防火墙吗?有防火墙,但节点被列为白名单,错误是间歇性的,有时它工作,有时它返回502个坏网关主机名中的多个ip地址(dns循环)?我如何检查?执行nslookup xx.com
nginx容器无法访问的接缝https://xx.com
有防火墙吗?有防火墙,但节点被列为白名单,错误是间歇性的,有时它工作,有时它返回502个坏网关主机名中的多个ip地址(dns循环)?如何检查?执行nslookup xx.com