Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[millipede]

Using IE11 w/ Windows 10, I am unable to connect to the DNR-202L. I get the "There is a problem with this website's security certificate" screen, but with no option to proceed anyway (which used to be there). I just did a full rest on the DNR, updated the firmware, and re-configured with the setup wizard, and this roadblock now appears. I added the URL for the DNR to the trusted sites list, but that did not help. Any known workarounds for this?

[FurryNutz]

Link>Welcome!

• What region are you located?

What FW version is currently loaded?

Try FF browser as well?
Clear all browser caches before logging on to the DNR.

[RYAT3]

I use http:// without issue. Does that work in your case?

I also tried https:// , I got the certificate error, clicked Continue, and was prompted username/password.

ie11, win10/1607/14393.693

[millipede]

Thanks! that works. I also found that copying and pasting the https URL into a freshly opened browser window at least gets the "continue" option link. Connecting from a shortcut or via the mydlink page showing cameras and other devices leads to a certificate error page without any option to continue. Adding the certificate to trusted lists did not help. An Explorer or Windows issue, apparently, and not new. Lots of reports now and then over the years, and so far no workarounds for this instance with this DNR.

[FurryNutz]

Does the same this happen in FF? Usually FF will display the error page however does let you had an exception.

Thanks! that works. I also found that copying and pasting the https URL into a freshly opened browser window at least gets the "continue" option link. Connecting from a shortcut or via the mydlink page showing cameras and other devices leads to a certificate error page without any option to continue. Adding the certificate to trusted lists did not help. An Explorer or Windows issue, apparently, and not new. Lots of reports now and then over the years, and so far no workarounds for this instance with this DNR.