This site can’t provide a secure connection

在Google chrome浏览器输入http的地址,自动解析成https的地址,并且页面显示显示“This site can’t provide a secure connection”错误。解决方案如下:亲测有效

【转】在本地使用Chrome调试网站的时候,有时候会出现"This site can't provide a secure connection 该网站无法提供安全的连接"的异常。原因就是此前在访问127.0.0.1的时候,因为某些配置出现了自动跳转,从http://127.0.0.1跳转到了https://127.0.0.1, 而现在调试网站,虽然没有了让其自动跳转的配置,但是Chrome浏览器记住了这个地址缓存了下来,依然还是自动跳转到了https.但是现在调试的网站又不支持https,所以Chrome就会提示该网站无法提供安全的连接。

解决办法:浏览器输入chrome://net-internals/#hsts, 配置Chrome,在Delete domain security policies中,输入localhost,然后点击delete. 有时候这样就可以清除缓存解决这个问题。如果还是不行的话,可以清除浏览器缓存试试,有时候这两步能解决这个问题。
————————————————

                        
原文链接:https://blog.youkuaiyun.com/sundacheng1989/article/details/125593836

SSL Report: aivisionxskino.com (8.163.27.185) Assessed on: Wed, 16 Jul 2025 08:47:44 UTC | Hide | Clear cacheScan Another » Assessment failed: No secure protocols supported Known Problems There are some errors that we cannot fix properly in the current version. They will be addressed in the next generation version, which is currently being developed. No secure protocols supported - if you get this message, but you know that the site supports SSL, wait until the cache expires on its own, then try again, making sure the hostname you enter uses the "www" prefix (e.g., "www.ssllabs.com", not just "ssllabs.com"). no more data allowed for version 1 certificate - the certificate is invalid; it is declared as version 1, but uses extensions, which were introduced in version 3. Browsers might ignore this problem, but our parser is strict and refuses to proceed. We'll try to find a different parser to avoid this problem. Failed to obtain certificate and Internal Error - errors of this type will often be reported for servers that use connection rate limits or block connections in response to unusual traffic. Problems of this type are very difficult to diagnose. If you have access to the server being tested, before reporting a problem to us, please check that there is no rate limiting or IDS in place. NetScaler issues - some NetScaler versions appear to reject SSL handshakes that do not include certain suites or handshakes that use a few suites. If the test is failing and there is a NetScaler load balancer in place, that's most likely the reason. Unexpected failure - our tests are designed to fail when unusual results are observed. This usually happens when there are multiple TLS servers behind the same IP address. In such cases we can't provide accurate results, which is why we fail. Common Error Messages Connect timed out - server did not respond to our connection request, sometimes before we are dynamically blocked when our tests are detected No route to host - unable to reach the server Unable to connect to server - failed to connect to the server, it usually happens due to firewall restrictions Connection reset - we got disconnected from the server Unrecognized SSL message, plaintext connection? - the server responded with plain-text HTTP on HTTPS port Received fatal alert: handshake_failure - this is either a faulty SSL server or some other server listening on port 443; if the SSL version of the web site works in your browser, please report this issue to us Failed to communicate with the secure server - No secure protocol supported. Possibly this server only supports a draft version of TLS 1.3 SSL Report v2.4.1 比较上一次的信息,再分析下原因
最新发布
07-17
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值