Mar 11

A number of models are experiencing problems displaying the Live View! on mydlink.com portal after the last Java update (Java 8 update 31). The problem is a resolts of the discontinue support of  SSL v3.0.

The following Products are affected by this update:

  • DCS-930L
  • DCS-932L
  • DCS-931L
  • DCS-933L
  • DCS-5009L
  • DCS-5010L
  • DCS-5020L
  • DCS-6045L
  • DCS-700L
  • DCS-800L
  • DCS-850L

An alternative way of monitoring your cameras:

    • Using the mydlink™ Lite mobile App  (available for iOS, Android and Windows Mobile devices)mydlinkLiteLogo      mydlink Lite
Store Links QR Links
GooglePlayLogo qr_code_android_mydlink-lite_tr
AppleStoreLogo qr_code_iOS_mydlink-lite_tr
WindowsStoreLogo qr_code_windows_mydlink-lite_tr

 

At this time, we are currently workign on a more permanent solution for this problem, for now, a workaround is available to temporarly allow the use of SSLv3.0 on the new version of Java.

Follow the steps to enable SSL 3.0 manually:

 

 


 

Windows PC Users :

 

Step 1: Open Windows Explorer and go to the following java library security file.

“C:\Program Files (x86)\Java\jre1.8.0_31\lib\security\java.security”  or
“C:\Program Files\Java\jre1.8.0_31\lib\security\java.security”.

 

A10980_image01


A10980_image02

 

Step 2:  Open “Notepad” in Administrator mode by right-clicking the mouse. Select “Run as administrator” in the context menu.
A10980_image03

 

Step 3:  Open the java.security file by right clicking the file, and “open with” Notepad.  The file should now be editable in clear text. Scroll down or Page Down to the last line and comment it out (make it invalid) by adding a # sign at the front of the line.

jdk.tls.disabledAlgorithms=SSLv3    <this is the last line of the java file>
# jdk.tls.disabledAlgorithms=SSLv3    <add the # sign to the front of it to make the line inactive>

 

A10980_image04

 

Step 4: Save the java file by clicking on the File manu and select “Save”.

 

Step 5:  Open Windows Explorer and navigate to the current “user” folder.

  • Go to C:\Users and select the user’s name. Replace <current user> with the name of the customer’s login.
  • The next portion may be hidden and needs to be manually added\Appdata\LocalLow\Sun\Java\Deployment. So the full path should be:
    C:\Users\<current user name>\AppData\LocalLow\Sun\Java\Deployment\deployment.properties

    A10980_image05
    A10980_image06

Step 6: Open the deployment.properties file by right clicking the file and open with Notepad.  The file should now be editable in clear text.

  • On the bottom line of the deployment.properties file add the following line:

deployment.security.SSLv3=true   << add this line to the bottom of the file>

A10980_image07
Step 7:  Save the deployment.properties file.

 

Step 8:  Save your work, close all browsers, restart browser, go to mydlink.com Login, select your camera, test your live footage

 

You should be able to log in mydlink portal to see your camera(s).  A more permanent solution is coming soon in a form of a firmware update.  If for any reason you still continue to have problems, contact our Technical Support Group for assistance.

 


 

Mac OS users:

 

Step 1:  Run Terminal. Open Spotlight Search, type Terminal to run application Terminal.

 

A10980_image08

Step 2:  Go to the Java security folder:

Type “cd /Library/Internet\Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/security/

 

A10980_image09

 

Step 3: Type “sudo vi java.security” , then enter your computer password to run the command.

 

A10980_image10

Step 4:   Scroll down or Page Down to the last line, type “i” to see INSERT

A10980_image11

 

Step 5: Add “#” in front of the line “jdk.tls.disabledAlgorithms=SSLv3” as “# jdk.tls.disabledAlgorithms=SSLv3”

 

A10980_image12

 

Step 6:  Press “esc” on your keyboard to clear the line Insert.

 

A10980_image13

 

Step 7: Type “:”, then type “wq!” to save the command.

 

A10980_image14

 

Step 8: Type “cd /Users/xxxxx/Library/Application\ Support/Oracle/Java/Deployment”. (Note: xxxxx is your user name on the Mac). If you are not sure, type “cd”, then type ”pwd” to retrieve your user name. Use this name to replace “xxxxx” on the command.

 

A10980_image15

 

Step 9: Type “sudo vi deployment.properties”, then enter your computer password to run the command.

 

A10980_image16

 

Step 10: Page down to the last line. Type “o” to see Insert on the bottom.

 

Step 11: Add the command line “deployment.security.SSLv3=true” and press “enter” on your keyboard.

 

A10980_image17

 

Step 12:  Press “esc” on your keyboard to clear the line Insert.

 

A10980_image18

 

Step 13: Type “:”; then type “wq!” to save the command.

 

A10980_image19

 

Step 14: Save your work, close all browsers, restart Chrome, Firefox, or Safari.

 

Step 15:  Go to mydlink.com Login, test your live footage.

 

You should be able to log in mydlink portal to see your camera(s).  A more permanent solution is coming soon in a form of a firmware update.  If for any reason you still continue to have problems, contact our Technical Support Group for assistance.

Be Sociable, Share!

Tags: , ,

9 Comments

  • At 2016.02.07 09:31, Angry said:

    This product is terrible. EVERYONE ELSE IN THE INDUSTRY modifies their application software to keep up with changes in the OS and browsers. You REALLY expect your computer illiterate users to be able to know A) to FIND THIS PAGE and B) be able to apply the information given here.

    Not ONLY THAT but you’re essentially asking them to self-inflict a security vulnerability onto their system.

    Terrible.

    • At 2016.03.03 09:02, Robert said:

      Agree 100%
      This is a shame.

      • At 2017.05.02 15:50, StarGzr said:

        Couldn’t agree more.

      • At 2016.02.15 18:47, diego said:

        really BAD !!!!!

        You cant expect your users to do this

        • At 2016.06.17 06:00, Vesa said:

          well, I did. But it did not make the difference

        • At 2016.03.25 05:15, Juha said:

          I have D-Link DSC-932L and DSC-5020L and running Windows 10 with the latest version of Firefox. I installed latest java versions, 32 and 64 bit and having problems to see live feed or modify motion detection hot areas. I did your tricks to modify security settings and added both IPs as http://x.x.x.x and https://x.x.x.x in the Java security settings via Control Panel, but didn’t help. I have also tried to downgrade Java but on Windows 10 I have not found a working version of Java for the cameras. I can modify other settings but not those where java is needed.

          • At 2017.05.08 20:40, Vaughn said:

            What about Linux. Everything was working fine with firefox last month and now none of my cameras are working. I am not going to use an app or get Windoz just to check my cameras. I tried chrome and the main page doesn’t even come up. Wish I had other cams.

            • At 2017.05.26 04:14, Conrad said:

              The cameras are not supported anymore. The promised firmware has never been provided..

              • At 2017.05.29 23:11, Alan Corey said:

                Agreed, the lack of Linux support is unexpected. I’ve had 7 cameras for a couple years, finally dug them out to use for wildlife photography. I thought I’d be able to get to the control interface over WiFi. I’m not sure it’s even going to FTP files over WiFi. My “router” is tethering through an Android phone, I don’t have access to the list of connected devices. Ah, maybe I’ve got it, look at the transfer log after an FTP upload. It’s a long shot that leaves me uncomfortable. Host names of devices end up in DNS, I can connect to other devices by name.


                (Required)
                (Required, will not be published)

                css.php