发布于2023-01-19 16:56 阅读(1069) 评论(0) 点赞(18) 收藏(5)
We have an instance of a nginx web server, that some of our applications use. And last time we started getting cURL error #35 - SSL connect error
. But we don't get it continuously just about 2-3 times per 100 requests. Requests go from different sources (C# app, Unix-app, some php scripts etc.) And I'm confused because we can't find a reason of this problem.
curl_setopt($ch, CURLOPT_SSLVERSION, 3);
makes a falirue at all.
What could it be?
From the libcurl website, it states:
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others
Certainly with the PHP scripts it should be possible to edit them so that there is some extra debug information available to help debug ( could write to a text file etc ) - if the error persists and there is no info in the debug info then at least you have eliminated one source. I don't know how you would do the same for the unix app or the c# app - there most likely would be a way.
作者:黑洞官方问答小能手
链接:http://www.phpheidong.com/blog/article/476838/0043bd106bbd7b00fa2d/
来源:php黑洞网
任何形式的转载都请注明出处,如有侵权 一经发现 必将追究其法律责任
昵称:
评论内容:(最多支持255个字符)
---无人问津也好,技不如人也罢,你都要试着安静下来,去做自己该做的事,而不是让内心的烦躁、焦虑,坏掉你本来就不多的热情和定力
Copyright © 2018-2021 php黑洞网 All Rights Reserved 版权所有,并保留所有权利。 京ICP备18063182号-4
投诉与举报,广告合作请联系vgs_info@163.com或QQ3083709327
免责声明:网站文章均由用户上传,仅供读者学习交流使用,禁止用做商业用途。若文章涉及色情,反动,侵权等违法信息,请向我们举报,一经核实我们会立即删除!