diff --git a/faq/failed-to-load-resource.md b/faq/failed-to-load-resource.md index 8d79823f..c2e6bfd2 100644 --- a/faq/failed-to-load-resource.md +++ b/faq/failed-to-load-resource.md @@ -19,31 +19,43 @@ You get an error message that says **"Failed to load resource: net::ERR_CERT_DAT ### Cause -By default, we use "127.0.0.1" for service connection. However, you may use our "local.dynamsoft.com" certificate by setting **Dynamsoft.WebTwainEnv.Host = "local.dynamsoft.com"** or **Dynamsoft.DWT.Host="local.dynamsoft.com"**. +By default, “127.0.0.1” is used for service connection. "127.0.0.1" uses a self-signed certificate because it is an internal IP address, if your environment requires high level security, self-signed certificates may not be accepted. Moreover, Android OS or Chrome OS does not accept connection between browsers and Dynamsoft Service via "127.0.0.1". -Ref: In which cases would I use local.dynamsoft.com instead of 127.0.0.1? +1. In case, you used our expired certificate - local.dynamsoft.com, as an official domain which uses a VeriSign’ed certificate. The old "local.dynamsoft.com" certificate expired on January 9th, 2023 and the new certificate will expire on December 8th, 2023 + > ___Please note:___ _all official certificates issued by 3rd party come with an expiry date - generally one year. This means that each year the certificate will need to be updated if local.dynamsoft.com is used._ -In this case, if you are trying to access an application that integrates a version of Dynamic Web TWAIN V15.3 ~ V17.2.5, you will get the error. Because the old "local.dynamsoft.com" certificate expired on January 9th, 2023. +2. Your own domain certificate expired. -### Resolution + -- For v17.1.1 or older versions, choose one of the following approaches: +### Resolution + +- **No High Level Security Requirement**: + + Set back to "127.0.0.1" by comment the line `Dynamsoft.WebTwainEnv.Host = "local.dynamsoft.com"` or `Dynamsoft.DWT.Host="local.dynamsoft.com"` out. + +- **[Highly Recommend] High Level Security Requirement** + +1. Set back to "127.0.0.1" by comment the line `Dynamsoft.WebTwainEnv.Host = "local.dynamsoft.com"` or `Dynamsoft.DWT.Host="local.dynamsoft.com"` out. +2. Replace the certificate of "127.0.0.1" with your own domain certificate and build Service MSI yourself. More information refer to [How can I change the certificate of the Dynamsoft Service?](https://www.dynamsoft.com/web-twain/docs/faq/change-dynamsoft-service-certificate.html). + + -- For v17.2 or higher versions, use the new API UpdateCert to automatically update the client side certificate before it expires. **Please go to dynamsoft.webtwain.install.js file in the Resource Folder and search the keyword "OnSSLCertInfo"**, add the following lines of code: +- For v17.2 or higher versions, you can use the new API UpdateCert to automatically update client side certificate before it expires. **Please go to dynamsoft.webtwain.install.js file in the Resource Folder and search the keyword "OnSSLCertInfo"**, add the following lines of code: ```javascript Dynamsoft.OnSSLCertInfo = function (sslExpiredDate) { if ((sslExpiredDate - new Date()) / 86400000 < 15) { // Automatically updates 15 days before expiration Dynamsoft.DWT.UpdateCert( - "https://demo.dynamsoft.com/DWT/Resources/dist/cert.zip", + "Url to download the new certificate.", //E.g. http://xxx.com/cert.zip. server.pem.ldsc & server_key.pem.ldsc should be in cert.zip. function () { //Success callback }, function (errorCode, errorString) { - console.log(errorString); + console.log(errorString); } ); } diff --git a/faq/index.md b/faq/index.md index f96cc377..4b591664 100644 --- a/faq/index.md +++ b/faq/index.md @@ -285,7 +285,7 @@ permalink: /faq/