Issue:
NetBotz 5.3.4 NET::ERR_CERT_INVALID error when connecting to web page in Chrome.
Product Line:
NetBotz 700 series
Environment:
Botzware 5.3.4 and potentially earlier
Chrome browser
Cause:
When using the default self signed cert on a NetBotz NBRK0750 or NBWL0755 running 5.3.4 firmware, it has been seen that you may get an error page showing "Your connection is not private" with the additional error "NET::ERR_CERT_INVALID" and the page never provides the option to proceede anyway.
This is due to a potentially malformed field in the self signed cert as well as an increased sensitivity to this in the latest Chrome browser.
Resolution:
This issue is resolved in Botzware 5.3.5.
Prior to upgrading, you can:
1: Use a different browser.
2: When on this page, click anywhere and simply type (without quotes) "thisisunsafe".
Once you log in using either option, you can also create your own SSL cert instead of using the self signed cert and subsequent logins should not have this issue. This should also be done after upgrading to 5.3.5 but you can also create a new self signed cert after the upgrade and the availability of the continue option should no longer be an issue.
NetBotz 5.3.4 NET::ERR_CERT_INVALID error when connecting to web page in Chrome.
Product Line:
NetBotz 700 series
Environment:
Botzware 5.3.4 and potentially earlier
Chrome browser
Cause:
When using the default self signed cert on a NetBotz NBRK0750 or NBWL0755 running 5.3.4 firmware, it has been seen that you may get an error page showing "Your connection is not private" with the additional error "NET::ERR_CERT_INVALID" and the page never provides the option to proceede anyway.
This is due to a potentially malformed field in the self signed cert as well as an increased sensitivity to this in the latest Chrome browser.
Resolution:
This issue is resolved in Botzware 5.3.5.
Prior to upgrading, you can:
1: Use a different browser.
2: When on this page, click anywhere and simply type (without quotes) "thisisunsafe".
Once you log in using either option, you can also create your own SSL cert instead of using the self signed cert and subsequent logins should not have this issue. This should also be done after upgrading to 5.3.5 but you can also create a new self signed cert after the upgrade and the availability of the continue option should no longer be an issue.
發佈於: 施耐德電機Taiwan
