为什么Nginx可能会通过不正确的ssl证书?

如何解决为什么Nginx可能会通过不正确的ssl证书?

我在单个nginx服务器上托管了两个域,例如。 a.com和b.com。 Nginx用作反向代理,必须将https请求作为http传递给后端。您可以在下面找到a.com的配置(b.com具有相同的结构,但链接到另一个ssl文件):

upstream webservers {
....
}
server {
        listen 443 ssl;

        server_name a.com;

        ssl_certificate /etc/nginx/ssl/a.crt;
        ssl_certificate_key /etc/nginx/ssl/a.key;
        ssl_dhparam /etc/nginx/ssl/default.dh;

        location / {
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_pass http://webservers;
        }
}

不幸的是,当我测试curl https://b.com时,失败并显示curl: (60) SSL: no alternative certificate subject name matches target host name b.com。当我尝试从浏览器打开它时,它失败并显示NET::ERR_CERT_COMMON_NAME_INVALID,并且表明它使用a.com证书。

我的错误在哪里?

Upd#1

我必须允许HTTP临时解决问题。

openssl s_client -connect b.com:443 -prexit
140648924489024:error:2008F002:BIO routines:BIO_lookup_ex:system lib:../crypto/bio/b_addr.c:726:Name or service not known
connect:errno=22
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 bytes
Verification: OK
---
New,(NONE),Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

配置:

# configuration file /etc/nginx/sites-enabled/a.com:
upstream a-webservers {
        server 192.168.0.252 max_fails=3 fail_timeout=30s;
        server 192.168.0.252 max_fails=3 fail_timeout=30s;
}
server {
        listen 443 ssl;

        server_name a.com;

        error_log  /var/log/nginx/a.com-error.log;
        access_log  off;

        ssl_certificate /etc/nginx/ssl/a.crt;
        ssl_certificate_key /etc/nginx/ssl/a.key;
        ssl_dhparam /etc/nginx/ssl/default.dh;

        location / {
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_pass http://a-webservers;
        }
}

# configuration file /etc/nginx/sites-enabled/b.com:
upstream b-webservers {
        server 192.168.0.252 max_fails=3 fail_timeout=30s;
        server 192.168.0.252 max_fails=3 fail_timeout=30s;
}
server {
        listen 80;
        listen 443 ssl;

        server_name b.com;

        error_log  /var/log/nginx/b.com-error.log;
        access_log  off;

        ssl_certificate /etc/nginx/ssl/b.crt;
        ssl_certificate_key /etc/nginx/ssl/b.key;
        ssl_dhparam /etc/nginx/ssl/default.dh;

        location / {
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_pass http://b-webservers;
        }
}

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-