简体   繁体   English

上游在访问https域时从上游读取响应头时没有发送有效的HTTP / 1.0头

[英]upstream sent no valid HTTP/1.0 header while reading response header from upstream when access https domain

When access my domain https://rancher1.208.com,the docker's nginx throw this error: 当访问我的域https://rancher1.208.com时,docker的nginx会抛出此错误:

2019/06/11 00:19:42 [error] 6#6: *40 upstream sent no valid HTTP/1.0 header while reading response header from upstream, client: 101.24.11.112, server: rancher.208.com, request: "GET / HTTP/1.1", upstream: "http://172.19.104.231:4431/", host: "rancher1.208.com"

This is my ssl config: 这是我的ssl配置:

    listen 443 ssl;
    listen [::]:443 ssl;
    ssl_certificate /etc/nginx/conf.d/cert/rancher1.208.com/fullchain1.pem;
    ssl_certificate_key /etc/nginx/conf.d/cert/rancher1.208.com/privkey1.pem;

    server_name rancher1.208.com;

Where is going wrong?should I redirect 80 to 443? 哪里出错了?我应该将80重定向到443吗?

Check you proxy address to use https: 检查代理地址以使用https:

location / {
        proxy_pass https://rancher;
        index index.html index.htm;
    }

Pay attention the proxy_pass is https not http. 注意proxy_pass是https而不是http。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Nginx HTTPS负载平衡上游没有发送有效的HTTP / 1.0标头 - Nginx HTTPS Load Balancing upstream sent no valid HTTP/1.0 header 上游从上游读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream 在 Keycloak 中读取来自上游的响应 header 时,上游发送了太大的 header - Upstream sent too big header while reading response header from upstream in Keycloak Nginx上游在从上游读取响应头时发送了太大的头 - Nginx upstream sent too big header while reading response header from upstream 上游从客户端,客户端(nginx,清漆)读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream, client (nginx, varnish) 如何修复上游从上游读取响应头时发送过大的头? - how to fix upstream sent too big header while reading response header from upstream? Nginx Web 服务器错误 - 从上游读取响应标头时,上游发送的标头太大 - Nginx Web Server Error - upstream sent too big header while reading response header from upstream 从上游读取响应标头时,上游发送了太大的标头 - upstream sent too big header while reading response header from upstream k8s NGINX 入口控制器上的请求失败,并显示“从上游读取响应标头时上游发送的标头太大” - Request on k8s NGINX ingress controller fails with “upstream sent too big header while reading response header from upstream” PHP 升级后的 nginx 错误:FastCGI 在 stderr 中发送:“”同时从上游读取响应标头 - nginx error after PHP upgrade: FastCGI sent in stderr: " " while reading response header from upstream
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM