首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >当我将nginx放在Tomcat前面时,如何修复net::ERR_SSL_PROTOCOL_ERROR错误?

问当我将nginx放在Tomcat前面时,如何修复net::ERR_SSL_PROTOCOL_ERROR错误?
EN

Server Fault用户
提问于 2021-12-04 06:57:13
回答 2查看 7.1K关注 0票数 0

当我将nginx放在Tomcat前面时,如何修复net::ERR_SSL_PROTOCOL_ERROR错误?

代码语言:javascript
复制
#user nobody;
worker_processes 1;

#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;

#pid logs/nginx.pid;


events {
    worker_connections 1024;
}


http {
    include 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 logs/access.log main;

    sendfile on;
    #tcp_nopush on;

    #keepalive_timeout 0;
    keepalive_timeout 65;

    upstream tomcat {
        server 127.0.0.1:8330;
    }

    charset utf-8;



    #gzip on;

    server {
        listen 8331;
        server_name localhost;

        # return 301 https://$host$request_uri;
        #charset koi8-r;

        #access_log logs/host.access.log main;

        location / {
            # root html;
            # index index.html index.htm;
            # proxy_pass http://sgmng.pluggolf.com;

            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header X-NginX-Proxy true;

            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "Upgrade";
            proxy_set_header Origin "";
            # new

            # Copy the upstream path set above
            proxy_pass https://tomcat;
            # proxy_redirect off;
            charset utf-8;
        }

        #error_page 404 /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page 500 502 503 504 /50x.html;
        location = /50x.html {
            root html;
        }

        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
        # proxy_pass http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        #location ~ \.php$ {
        # root html;
        # fastcgi_pass 127.0.0.1:9000;
        # fastcgi_index index.php;
        # fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
        # include fastcgi_params;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        # deny all;
        #}
    }


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    # server {
    # listen 8080;
    # listen somename:8080;
    # server_name somename alias another.alias;

    # location / {
    # root html;
    # index index.html index.htm;
    # }
    # }


    # HTTPS server
    
    server {
       listen 8332 ssl;
       server_name localhost;

       charset utf-8;

       ssl_certificate D:/service/cbdc_dt/nginx/cert/plusity.crt;
       ssl_certificate_key D:/service/cbdc_dt/nginx/cert/plusity.key;

    # ssl_session_cache shared:SSL:1m;
    # ssl_session_timeout 5m;

       ssl_ciphers HIGH:!aNULL:!MD5;
       ssl_prefer_server_ciphers on;

       location / {
        # root html;
        # index index.html index.htm;
        proxy_pass http://tomcat;

        proxy_set_header Host $http_host;
        proxy_set_header X-Real_IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            # proxy_set_header X-Forwarded-Proto $scheme;
            # proxy_set_header X-NginX-Proxy true;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection '';
        proxy_set_header Origin "";
        proxy_http_version 1.1;
        chunked_transfer_encoding off;

        proxy_buffering off;
        proxy_cache off;
        proxy_read_timeout 7d;
        proxy_redirect off;
        charset utf-8;
       }
    }

}

将ssl应用于端口8331和8332的所有请求之后,我编写了重定向到tomcat端口8330的代码。

但是,问题是,如果像这样通过nginx转到8330,就会发生GET https://serverIP:8330/itf/subscribe net::ERR_SSL_PROTOCOL_ERROR错误。

当nginx不存在时,/itf/subscribe正常工作。

但是,在https地址内调用时似乎存在问题。

我想知道怎样才能解决这个问题。

诚挚的问候!

EN

回答 2

Server Fault用户

发布于 2021-12-04 08:03:01

根据您的nginx配置,端口8330由您的上游服务器(Tomcat)处理。如果您还没有配置Tomcat来使用SSL,那么当您用https URL连接到它时,就会得到SSL错误。

使用您的配置,您需要连接到https://example.com:8332/以使用SSL。这将连接到为SSL配置的nginx端口,然后nginx代理对Tomcat服务器的请求。

票数 1
EN

Server Fault用户

发布于 2022-08-05 15:31:20

我也犯了同样的错误。

首先,当我使用SSL访问IP/域时,我看到了路由器的登录页面。这是因为它还在端口443上提供自己的网页。

我的解决方案是将端口443从任意地址转发到我的服务器-IP:443(将端口转发规则添加到我的路由器)。

代码语言:javascript
复制
Source: *   Port: 443   TO    Destination: server-IP   Port: 443

解决了我的问题。

票数 0
EN
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://serverfault.com/questions/1085363

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档