Docker Swarm模式下多Nginx反向代理配置异常排查
Docker Swarm集群中Nginx副本导致HTTP_HOST头重复的问题排查与解决
我正在配置Docker Swarm集群,计划部署3个Nginx副本作为反向代理与负载均衡。目前发现后端容器收到无效请求,核心错误为:
Invalid HTTP_HOST header: 'archive.tomhanfriends.com,archive.tomhanfriends.com,archive.tomhanfriends.com'. The domain name provided is not valid according to RFC 1034/1035
已完成以下检查:
- DNS配置正常,ping可连通
- Nginx配置文件语法检查通过(
nginx -t) - Docker Swarm服务处于同一网络,可正常通信
- Nginx的Docker Compose可正常运行
- Archivebox的Docker Compose可正常运行
相关配置
Docker Swarm集群架构

Nginx Docker配置
version: '3.8' services: nginx: image: docker.io/nginx:latest restart: unless-stopped ports: - '80:80' - '443:443' volumes: - ./nginx/data/conf/conf.d:/etc/nginx/conf.d - ./nginx/data/conf/ssl:/etc/nginx/ssl - ./nginx/data/logs:/var/log/nginx - ./nginx/data/www:/usr/share/nginx/html deploy: replicas: 3 placement: constraints: - node.role == manager restart_policy: condition: on-failure delay: 5s max_attempts: 3 window: 120s networks: - infrastructure - ops networks: infrastructure: external: true ops: external: true
Nginx主配置
user nginx; worker_processes auto; error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid; events { worker_connections 1024; } http { tcp_nopush on; tcp_nodelay on; types_hash_max_size 2048; server_tokens off; include /etc/nginx/mime.types; default_type application/octet-stream; ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE ssl_prefer_server_ciphers on; 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; gzip on; gzip_vary on; gzip_proxied any; gzip_comp_level 6; gzip_buffers 16 8k; gzip_http_version 1.1; gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript; proxy_connect_timeout 300s; proxy_read_timeout 300s; proxy_send_timeout 300s; proxy_buffer_size 128k; proxy_buffers 4 128k; proxy_busy_buffers_size 256k; proxy_temp_file_write_size 256k; proxy_headers_hash_max_size 1024; proxy_headers_hash_bucket_size 128; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; include /etc/nginx/conf.d/*.conf; }
Archivebox Nginx配置
server { listen 80; listen 443 ssl; charset utf-8; server_name archive.tomhanfriends.com; .... omit for ssl location / { proxy_pass http://ops_archivebox:8000/; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_header Host $host; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } error_page 500 502 503 504 /50x.html; location = /50x.html { root html; } }
问题根源与解决方法
1. 重复设置Host头是核心原因
观察Archivebox的Nginx配置,location /块中重复设置了三次Host头:
proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_header Host $host; proxy_set_header Host $http_host;
Nginx默认会将同一请求头的多次设置值用逗号拼接,最终导致后端收到重复的域名,触发RFC 1034/1035的格式错误。
2. 修复步骤
- 清理重复的
proxy_set_header Host语句,保留一条即可(推荐用$host,它会自动去掉端口号,更符合规范)。修改后的location /块:location / { proxy_pass http://ops_archivebox:8000/; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } - 另外,Nginx主配置中已经全局设置了
proxy_set_header Host $host;,如果不需要子配置覆盖,也可以直接删除子配置中的Host头设置,彻底避免重复。
3. Swarm集群额外注意事项
由于部署了3个Nginx副本,需确保:
- 所有Nginx副本通过挂载统一配置卷保持配置一致(当前配置已满足)
- Swarm端口映射
ports: - '80:80'会自动实现负载均衡,无需额外调整 - 若使用外部负载均衡器,需确认其不会重复添加Host头
内容的提问来源于stack exchange,提问作者TomHan
相关产品推荐
相关产品推荐

