forked from docs/doc-exports
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: zhoumeng <zhoumeng35@huawei.com> Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
15 lines
1.6 KiB
HTML
15 lines
1.6 KiB
HTML
<a name="elb_faq_211003"></a><a name="elb_faq_211003"></a>
|
|
|
|
<h1 class="topictitle1">Why Is Access to Backend Servers Still Abnormal Even If I Have Created a Certificate?</h1>
|
|
<div id="body0000001195558531"><p id="elb_faq_211003__p1589411522137">The following are possible causes:</p>
|
|
<ul id="elb_faq_211003__ul11481165017168"><li id="elb_faq_211003__li248115013167">You have created a certificate on the ELB console, but you do not have an HTTPS listener.<p id="elb_faq_211003__p1923482717141"><a name="elb_faq_211003__li248115013167"></a><a name="li248115013167"></a>To solve this problem, perform the following steps:</p>
|
|
<ul id="elb_faq_211003__ul1398044316148"><li id="elb_faq_211003__li171086115500">Continue using the current listener and install the certificate on the backend server.</li><li id="elb_faq_211003__li1898034391416">Delete the current listener, add an HTTPS listener, and bind a certificate to the HTTPS listener.</li></ul>
|
|
</li><li id="elb_faq_211003__li1748119502162">You have created a certificate on the <strong id="elb_faq_211003__b9288164014558">Certificates</strong> page and are using an HTTPS listener, but you have not bound the certificate to the listener.</li><li id="elb_faq_211003__li848115001614">Your certificate has expired.</li><li id="elb_faq_211003__li15482165010167">The domain name is different from the one specified when you create the certificate.</li><li id="elb_faq_211003__li548217505165">A certificate chain is used, but its format is incorrect.</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0205.html">Certificates</a></div>
|
|
</div>
|
|
</div>
|
|
|