AlphaWu

AlphaWu

V2EX 第 3117 号会员,加入于 2010-11-19 19:31:00 +08:00
AlphaWu 最近回复了
Win11 确实有这么个问题,太烦人了。
我的解决方案:
自己写一个 windows 服务,定时去读取一个 txt 的 url 地址,如果读到 0 ,就重启。一般重启后就正常了。
@kof21411 不会的,我已经测试了,都正常,IP 的 https 可以访问,IP 之下的其他域名的 https 都可以正常访问。
放到一个文件里面,把 ip 的配置放到上面。

server {
listen 443 ssl http2;
server_name 192.168.200.136;
root /tmp/webroot/ip;
index index.html;
access_log /data/logs/ip_access.log;
ssl_certificate /etc/nginx/ssl/server.crt;
ssl_certificate_key /etc/nginx/ssl/server.key;
ssl_session_timeout 5m;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
}
server {
listen 80;
server_name www.domain.com;
return 301 https://www.domain.com$request_uri;
}
server {
#listen 443 ssl;
listen 443 ssl;
server_name www.domain.com;
access_log /data/logs/www.log main;
add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload";
ssl_certificate /etc/nginx/ssl/fullchain.cer;
ssl_certificate_key /etc/nginx/ssl/fullchain.key;
ssl_dhparam /etc/nginx/dhparam.pem;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
add_header X-Frame-Options SAMEORIGIN;
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";
ssl_protocols TLSv1.3;
ssl_ciphers TLS13-AES-256-GCM-SHA384:TLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-128-CCM-8-SHA256:TLS13-AES-128-CCM-SHA256:EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+ECDSA+AES128:EECDH+aRSA+AES128:RSA+AES128:EECDH+ECDSA+AES256:EECDH+aRSA+AES256:RSA+AES256:EECDH+ECDSA+3DES:EECDH+aRSA+3DES:RSA+3DES:!MD5;
return 222;
}
关于   ·   帮助文档   ·   博客   ·   API   ·   FAQ   ·   实用小工具   ·   5487 人在线   最高记录 6679   ·     Select Language
创意工作者们的社区
World is powered by solitude
VERSION: 3.9.8.5 · 43ms · UTC 08:36 · PVG 16:36 · LAX 00:36 · JFK 03:36
Developed with CodeLauncher
♥ Do have faith in what you're doing.