-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
关于使用自签名证书问题 #1830
Labels
bug
Something isn't working
Comments
我也遇到类似的问题,部署的是根证书,但是不确定为什么Fastgpt没有去调用这个根证书,也是显示self-signed certificate in certificate chain。 |
没遇到过,一般环境中,发起方不需要配置任何证书,除非被请求方有特殊要求。 |
确实是对端要求要有证书,所以对于fastgpt这边,我也要安装证书,但是这个证书应该怎么安装呢
发自我的iPhone
…------------------ 原始邮件 ------------------
发件人: Archer ***@***.***>
发送时间: 2024年7月4日 15:31
收件人: labring/FastGPT ***@***.***>
抄送: zxx74520 ***@***.***>, Author ***@***.***>
主题: Re: [labring/FastGPT] 通过FASTGPT去调用其他应用接口的时候报证书问题 (Issue #1830)
没遇到过,发起方一般环境中,不需要配置任何证书,除非被请求方有特殊要求
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
默认情况下,fastgpt 安装了通用根证书 对于自签名证书,由于没有任何可信证书,解决思路有如下几种:
var req = https.request({
host: 'https://self-signed.example.com',
port: 443,
path: '/',
method: 'GET',
rejectUnauthorized: false, // <-修改这个参数为 false,默认为 true
requestCert: true,
agent: false
},...)
var req = https.request({
host: 'https://self-signed.example.com',
port: 443,
path: '/',
method: 'GET',
ca: [<ca-string[]>, {encoding: 'utf-8'})], // <-这里是自签名证书的根证书字符串
requestCert: true,
agent: false
},...)
|
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
我这边在通过fastgpt去调用我们自己部署的一个应用的时候报证书问题(该应用我们是布置了自签发证书)
报错信息如下:
{
"error": {
"message": "self-signed certificate in certificate chain",
"name": "Error",
"method": "post",
"baseURL": "
http://fastgpt-xxxxxx:3000"
,
"url": "
https://awx.apps.os.xxxxxx.com/api/v2/job_templates/116/launch/"
,
"code": "SELF_SIGNED_CERT_IN_CHAIN"
}
}
请问,该问题该如何解决?是否是需要给fastgpt也要部署相应的自签发证书?如果是的话,请问fastgpt应该如何配置自签发证书?
The text was updated successfully, but these errors were encountered: