blocks|key|182711|text|您可能没有在SQL+VM的受信任根存储区中安装CA签名证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182712|如果连接字符串中包含Encrypt=True，请将其设置为off+(不推荐)，或者在连接字符串中添加以下内容：|offset|length|style|CODE|182713|TrustServerCertificate=True|code-block|syntax|javascript|182714|如果您没有安装自签名证书供SQL+Server使用，SQL+server将创建一个自签名证书，但调用方不会信任它，因为它不是CA签名的，除非您告诉连接字符串在默认情况下信任任何服务器证书。|182715|从长远来看，我建议利用Let's+Encrypt免费从已知的可信CA获得CA签名证书，并将其安装在VM上。不要忘记将其设置为自动刷新。您可以在SQL+Server联机丛书“加密层次结构”和“使用加密而不进行验证”的主题下阅读有关此主题的更多信息。|182716|entityMap|0|LINK|mutability|MUTABLE|url|https://letsencrypt.org/^0|0|A|C|0|0|0|B|D|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

You likely don't have a CA signed certificate installed in your SQL VM's trusted root store.

If you have <code>Encrypt=True</code> in the connection string, either set that to off (not recommended), or add the following in the connection string:

<pre><code>TrustServerCertificate=True
</code></pre>

SQL Server will create a self-signed certificate if you don't install one for it to use, but it won't be trusted by the caller since it's not CA-signed, unless you tell the connection string to trust any server cert by default.

Long term, I'd recommend leveraging <a href="https://letsencrypt.org/" rel="noreferrer">Let's Encrypt</a> to get a CA signed certificate from a known trusted CA for free, and install it on the VM. Don't forget to set it up to automatically refresh. You can read more on this topic in SQL Server books online under the topic of "Encryption Hierarchy", and "Using Encryption Without Validation".

blocks|key|185545|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|185546|📷|atomic|offset|length|185547|如果您使用的是SQL+Management+Studio，请转到连接属性并单击“已认证的信任服务器”|185548|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/88f2053a99bce797bb11dda8b38760a0.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

<a href="https://i.stack.imgur.com/92Eu6.png" rel="noreferrer"><img src="https://i.stack.imgur.com/92Eu6.png" alt="If you&#39;re using SQL Management Studio, please goto connection properties and click on &quot;Trust server certificated&quot;"></a>
If you're using SQL Management Studio, please goto connection properties and click on "Trust server certificated"

blocks|key|3009628|text|如果您在尝试使用SSMS连接时看到此错误消息，请将TrustServerCertificate=True添加到其他连接参数中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3009629|entityMap^0|P|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you're seeing this error message when attempting to connect using SSMS, add <code>TrustServerCertificate=True</code> to the Additional Connection Parameters.

blocks|key|2797451|text|我决定添加另一个答案，因为这篇文章作为谷歌对这个错误的第一个结果弹出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2797452|如果您在2022年1月之后收到此错误，可能是在从System.Data.SqlClient+Microsoft.Data.SqlClient+迁移到Microsoft.Data.SqlClient或仅将更新到4.0.0或更高版本之后，这是因为MS引入了一个突破性的更改：|offset|length|style|BOLD|CODE|2797453|2797454|+https://docs.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace?view=sql-server-ver15#breaking-changes-in-40|blockquote|2797455|2797456|4.0中的重大变化|2797457|默认情况下，已将Encrypt连接字符串属性更改为true。|2797458|Encrypt连接设置的默认值已从false更改为true。随着云数据库的使用越来越多，并且需要确保这些连接的安全，是时候进行这种破坏向后兼容性的更改了。|2797459|确保在需要加密时连接失败|2797460|在客户端加密库被禁用或不可用的情况下，当Encrypt设置为true或服务器需要加密时，可能会建立未加密的连接。|2797461|2797462|Rick+Strahl在on+his+blog上发布了详细的解释|2797463|更改是在this+SqlClient+pull-request+in+August+2021,+where+there+is+additional+discussion+about+the+change中进行的。|2797464|快速解决方法是将Encrypt=False添加到连接字符串中。|2797465|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace?view=sql-server-ver15#breaking-changes-in-40|1|https://weblog.west-wind.com/posts/2021/Dec/07/Connection-Failures-with-MicrosoftDataSqlClient-4-and-later|2|https://github.com/dotnet/SqlClient/pull/1210^0|0|O|L|1A|O|1Z|1S|O|L|1A|O|22|O|0|0|1|41|0|0|0|0|8|7|P|4|0|0|7|H|5|P|4|0|0|K|7|U|4|0|0|C|B|1|0|4|2P|2|0|8|D|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]|$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]|$D|1O|E|1P|F|H]|$D|1Q|E|1R|F|H]|$D|1S|E|1T|F|H]]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1V|8|@]|9|@$D|1W|E|1X|1|1Y]]|A|$]]|$1|M|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|20|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|21|8|@$D|22|E|23|F|H]|$D|24|E|25|F|H]]|9|@]|A|$]]|$1|R|3|S|5|6|7|26|8|@$D|27|E|28|F|H]|$D|29|E|2A|F|H]|$D|2B|E|2C|F|H]]|9|@]|A|$]]|$1|T|3|U|5|6|7|2D|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2E|8|@$D|2F|E|2G|F|H]|$D|2H|E|2I|F|H]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2K|8|@]|9|@$D|2L|E|2M|1|2N]]|A|$]]|$1|10|3|11|5|6|7|2O|8|@]|9|@$D|2P|E|2Q|1|2R]]|A|$]]|$1|12|3|13|5|6|7|2S|8|@$D|2T|E|2U|F|H]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]|1C|$5|17|18|19|A|$1A|1D]]|1E|$5|17|18|19|A|$1A|1F]]]]

I decided to add another answer, because this post pops-up as the first Google result for this error.
If you're getting this error after January 2022, possibly after migrating from <code>System.Data.SqlClient</code> to <code>Microsoft.Data.SqlClient</code> or just updating <code>Microsoft.Data.SqlClient</code> to version 4.0.0 or later, it's because MS has introduced a breaking change::
<blockquote>
<a href="https://docs.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace?view=sql-server-ver15#breaking-changes-in-40" rel="noreferrer">https://docs.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace?view=sql-server-ver15#breaking-changes-in-40</a>
<h2>Breaking changes in 4.0</h2>
<h3>Changed <code>Encrypt</code> connection string property to be <code>true</code> by default.</h3>
The default value of the <code>Encrypt</code> connection setting has been changed from <code>false</code> to <code>true</code>. With the growing use of cloud databases and the need to ensure those connections are secure, it's time for this backwards-compatibility-breaking change.
<h3>Ensure connections fail when encryption is required</h3>
In scenarios where client encryption libraries were disabled or unavailable, it was possible for unencrypted connections to be made when <code>Encrypt</code> was set to <code>true</code> or the server required encryption.
</blockquote>
Rick Strahl has posted a detailed explanation <a href="https://weblog.west-wind.com/posts/2021/Dec/07/Connection-Failures-with-MicrosoftDataSqlClient-4-and-later" rel="noreferrer">on his blog</a>
The change was made in <a href="https://github.com/dotnet/SqlClient/pull/1210" rel="noreferrer">this SqlClient pull-request in August 2021, where there is additional discussion about the change</a>.
The quick-fix is to add <code>Encrypt=False</code> to your connection-strings.

blocks|key|183597|text|如果你试图在Visual+Studio2015中通过数据连接访问它，并得到上面的错误，那么转到高级并将错误的TrustServerCertificate=True设置为消失。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|183598|entityMap^0|1I|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If You are trying to access it through Data Connections in Visual Studio 2015, and getting the above Error, Then Go to Advanced and set 
<code>TrustServerCertificate=True</code>
for error to go away.

blocks|key|181478|text|虽然一般的答案本身是正确的，但我发现它对我的SQL+Server导入和导出向导导向问题来说还不够深入。假设您有一个有效的(并且是自动的)基于Windows安全的登录：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181479|ConnectionString|offset|length|style|BOLD|181480|Data+Source=localhost;+
Initial+Catalog=<YOUR+DATABASE+HERE>;+
Integrated+Security=True;+
Encrypt=True;+
TrustServerCertificate=True;+
User+Instance=False|code-block|syntax|javascript|181481|这可以是您的完整ConnectionString+(全部在一行上)，也可以将这些值单独应用于它们的字段。|181482|entityMap^0|0|0|G|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

While the general answer was in itself correct, I found it did not go far enough for my SQL Server Import and Export Wizard orientated issue. Assuming you have a valid (and automatic) Windows Security based login:
ConnectionString
<pre><code>Data Source=localhost; 
Initial Catalog=&lt;YOUR DATABASE HERE&gt;; 
Integrated Security=True; 
Encrypt=True; 
TrustServerCertificate=True; 
User Instance=False
</code></pre>
That can either be your complete ConnectionString (all on one line), or you can apply those values individually to their fields.

blocks|key|181443|text|我在通过SSMS将Excel数据导入SQLDatabase时遇到了这个问题。解决方案是在安全部分中设置TrustServerCertificate+=+True|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181444|entityMap^0|1F|T|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I got this Issue while importing Excel data into SQLDatabase through SSMS. The solution is to set <code>TrustServerCertificate = True</code> in the security section

blocks|key|183661|text|从IIS访问SQLServer时遇到了同样的问题。添加TrustServerCertificate=True无济于事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|183662|我可以在MS文档中看到注释：请确保SQLServer服务帐户有权访问您正在使用的TLS证书。(NT服务\MSSQLSERVER)|offset|length|style|BOLD|183663|打开personal+store，右键单击证书->+manage+private+keys+->，添加SQL+service+account并给予完全控制。|183664|重新启动SQL服务。啊，真灵。|183665|entityMap^0|0|E|1E|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Got hit by the same issue while accessing SQLServer from IIS. Adding TrustServerCertificate=True didnot help. 

Could see a comment in MS docs: Make sure the SQLServer service account has access to the TLS Certificate you are using. (NT Service\MSSQLSERVER)

Open personal store and right click on the certificate -> manage private keys -> Add the SQL service account and give full control.

Restart the SQL service. It worked.

blocks|key|183627|text|我在尝试运行分析器时遇到了这个错误，即使我的连接检查了信任服务器证书，并且我在高级部分中添加了TrustServerCertificate=True。我切换到以管理员身份运行的SSMS实例，分析器启动时没有任何问题。(我之前发现，当我的本地连接也需要很长时间才能连接时，以管理员身份运行是有帮助的)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|183628|entityMap^0|1B|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I ran into this error trying to run the profiler, even though my connection had Trust server certificate checked and I added <code>TrustServerCertificate=True</code> in the Advanced Section. I changed to an instance of SSMS running as administrator and the profiler started with no problem. (I previously had found that when my connections even to local took a long time to connect, running as administrator helped).

blocks|key|185694|text|对于那些不喜欢TrustServerCertificate=True答案的人，如果您有足够的访问权限，可以导出SQL+Server证书并将其安装在您尝试连接的位置。这可能不适用于SQL+Server自生成的证书，但如果您使用的是类似New-SelfSignedCertificate的证书，则可以使用MMC导出证书，然后在客户端使用MMC导入证书。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|185695|在SQL+Server上：|185696|将证书管理单元添加到证书>个人>+Certificate|185697|Select新证书，右键单击并选择所有任务>管理私钥(此步骤和下一步是使用密钥的一部分)|unordered-list-item|185698|
|185699|添加运行SQL+|185700|185701|的身份(如果有疑问，请在服务中查找身份)并读取新证书，右键单击并选择所有任务>+Export...|185702|185703|Use默认设置并另存为文件。|185704|185705|在客户端：|185706|使用具有相同管理单元选项的彩信，在证书>受信任的根证书颁发机构中，右键单击证书，然后选择所有任务>+Import...|185707|Import+先前导出的文件|185708|185709|(我在同一台服务器上执行所有操作，在重新启动SQL实例之前，SSMS仍然存在问题。然后我可以在没有信任的情况下加密连接..。选中复选框)|185710|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate?view=windowsserver2019-ps^0|7|R|38|P|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|F|3|G|5|6|7|1K|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1M|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1N|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1O|8|@]|D|@]|E|$]]|$1|Q|3|N|5|6|7|1P|8|@]|D|@]|E|$]]|$1|R|3|S|5|L|7|1Q|8|@]|D|@]|E|$]]|$1|T|3|N|5|6|7|1R|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|1S|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1U|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1V|8|@]|D|@]|E|$]]|$1|11|3|12|5|L|7|1W|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|1X|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|16|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|17|$18|$5|19|1A|1B|E|$1C|1D]]]]

For those who don't like the <code>TrustServerCertificate=True</code> answer, if you have sufficient access you can export the SQL Server certificate and install where you're trying to connect from. This probably doesn't work for a SQL Server self-generated certificate but if you used something like <a href="https://docs.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate?view=windowsserver2019-ps" rel="nofollow noreferrer">New-SelfSignedCertificate</a> you can use MMC to export the certificate, then MMC on the client to import it.
On SQL Server:
<ul>
<li>In MMC add the certificate Snap-In</li>
<li>Browse to Certificates &gt; Personal &gt; Certificate</li>
<li>Select the new certificate, right-click, and select All Tasks &gt; Manage Private Keys (this step and the following is part of making the key work with SQL server)</li>
<li>Add the identity running SQL Server (look the identity up in Services if in doubt) with READ permission.</li>
<li>Select the new certificate, right-click, and select All Tasks &gt; Export...</li>
<li>Use default settings and save as a file.</li>
</ul>
On the client:
<ul>
<li>Use MMS with the same snap-in choices and in Certificates &gt; Trusted Root Certification Authorities right-click Certificates and select All Tasks &gt; Import...</li>
<li>Import the previously exported file</li>
</ul>
(I was doing everything on the same server and still had issues with SSMS complaining until I restarted the SQL instance. Then I could connect encrypted without the Trust... checkbox checked)

blocks|key|181425|text|ssms客户端本身也可以做到这一点。只需打开ssms，插入服务器名称，然后从“连接属性”标题下的“选项”中确保选中“信任服务器证书”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181426|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The same can be achieved from ssms client itself. Just open the ssms, insert the server name and then from options under heading connection properties make sure Trust server certificate is checked.

blocks|key|181554|text|当我尝试连接到托管在Google+Cloud平台上的MS+SQL+Server实例时，在连接属性选项卡下使用带有未选中的信任服务器证书的SSMS时，我得到了相同的错误。通过将GCP提供的证书颁发机构导入到本地计算机的受信任根证书颁发机构列表中，我成功地信任了该证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181555|阅读完整的描述和解决方案here。|offset|length|181556|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/troubleshoot/sql/connect/error-message-when-you-connect^0|0|C|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I was getting the same error when trying to connect to MS SQL Server instance hosted on Google Cloud Platform using SSMS with unchecked Trust server certificate under the connection properties tab. I managed to trust the certificate by importing the GCP's provided certificate's authority to my local computer's list of Trusted Root Certification Authorities.
Read full description and resolution <a href="https://docs.microsoft.com/en-us/troubleshoot/sql/connect/error-message-when-you-connect" rel="nofollow noreferrer">here</a>.

blocks|key|3010055|text|好吧，在我的例子中，数据库是坏的。当我重新创建一个新的数据库名称时，这个错误得到了解决。这是来自SQL+Server数据库的错误。尝试重新创建一个新数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3010056|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Well in my case the Database was bad. When I re created a new database name the error got resolved. It's an error coming from SQL Server database. Try re creating a new database.

I am experiencing error when connecting MY DB which is in VM Role(I have SQL VM Role) from Azure Website. Both VM Role and Azure Website are in West zone. I am facing following issue:

<blockquote>
 SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)]
</blockquote>

I am able to connect to my DB using SSMS. 1433 port is open on my VM role. 
What is wrong with my connection?

"The certificate chain was issued by an authority that is not trusted" when connecting DB in VM Role from Azure website

Visual Studio

云数据库

SQL Server

数据库

服务器

TLS证书

Windows

从Azure网站连接VM角色(我具有SQL VM角色)的数据库时遇到错误。VM角色和Azure网站都位于West区域。我面临以下问题： SqlException (0x80131904)：已成功与服务器建立连接，但随后在登录过程中出错。(提供程序: SSL提供程序，错误:0-证书链由不受信任的颁发机构颁发。)]我可以使用SSMS连接到我的数据库。我的VM角色上的1433端口已打开。我的连接有什么问

问从Azure网站连接VM角色中的数据库时，“证书链由不受信任的颁发机构颁发”
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从Azure网站连接VM角色中的数据库时，“证书链由不受信任的颁发机构颁发”EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从Azure网站连接VM角色中的数据库时，“证书链由不受信任的颁发机构颁发”
EN