May 042017

It has come to our attention that Google Chrome is flagging calls to the DYMO Web Service as “not secure.”  This has been causing many of our users to have issues when printing through Chrome.

We have found the issue and have an internal fix undergoing QA testing at this very moment.  We estimate the fix will be released within 2 to 3 weeks. We apologize for the inconvenience at hope this will be resolved soon.

In the meantime, please consider several temporary fixes that have been identified within the below blog post:

The new DLS 8.6.1 release is now available!

  55 Responses to “Google Chrome “not secure warning” fix is on the way!”

  1. A temporary solution is to by enabling the following flag here chrome://flags/#allow-insecure-localhost.

  2. Why was Dymo using a self signed certificate? That’s pretty poor developer practice in 2017 and a pretty obvious security risk…

  3. There seems to be a disconnect between your tech support hotline and what is stated on this board. Here you state you are working on a fix but your tech support people say there is no issue. “If you have the latest driver and the correct paper we can help you” and they are blaming us! We almost dropped DYMO after the Chrome 45 fiasco. I was happy to see that you were working on a fix for this, however now with this tech support response to our clients, we will stop recommending your devices to our customers.

    • Hi David,

      I am sorry to hear you are having trouble with tech support. Please be aware the tech support hotline is designed for end-users/consumers and not intended for SDK developer support. Your best bet is to either post here or email our SDK support list at [email protected].


      • Jeff thanks for the response. Sorry I was not clearer, we are not calling the tech support hotline, our customers are.


  4. I recommend just using Firefox or IE until this issue is resolved. Both Firefox and IE are working fine with the lable printings.

  5. I would like to suggest that you build a browser extension that will communicate with a native app that does the printing to Dymo. This will be a lot more future proof solution. I am working on a similar integration that involves communicating with POS terminals.
    Here are the docs for Chrome, but the other browsers offer similar APIs.

    This is the second time Google messes up with our customers by adding restrictions and Dymo doesn’t keep up on time. Our software supports Dymo printers exclusively and people are starting to ask us to support other printers because they can’t print properly. So I think it is very important that you think this through and provide a more stable integration.

    • To make a long story short, we tried this with NPAPI, which led to tons of issues, especially given the fact that it is being phased out. This was the whole reason why we created a web service.

  6. Is this still on track? Can you provide an update on progress and ETA please and thank you!

  7. Updates from Dymo please? ETA?

  8. ETA please? We need this fix badly and are considering switching to another labelwriter manufacturer

  9. Any updates?


  10. Any update? I was quoted a fix time of 2 weeks, 3.5 weeks ago.

  11. Is there an official support email for the DYMO SDK? Any official support forum? Do you monitor the DYMO tag on Stack Overflow?

    I am not sure where to go to get help, I am having an issue but there doesn’t seem to be a good place to ask?? I posted a comment on a random blog post but no response…

  12. You posted that a fix would be estimated at 2-3 weeks. That was 3 weeks ago. Can we get an ETA?

  13. Can someone please check on the person responsible for watching this forum and make sure they are still alive?

  14. The Windows version is scheduled for release Tuesday May 30, 2017.

  15. Any idea when an OS X fix might be coming? A higher proportion of our OS X users seem to be impacted.

  16. Any news about the update?

  17. Also waiting for an update.
    We have built a solution in our web shop administration which is on https. As soon as we use the part of the administration that uses the web service, we get secure error. Need update ASAP!

  18. It would be a good idea to tag this thread with “DYMO Label Framework”, making it easier to find.

    • Give it the same tags as the one announcing the latest release; “DYMO Label Framework”, “Featured Software”, “News”, “SDK News”

  19. *** UPDATE *** May 30, 2017

    Here is the latest release! Please feel free to reply here with your questions, comments, and other feedback!

  20. Am I the only one that get error while trying to print?
    Request URL: https localhost:41951/DYMO/DLS/Printing/PrintLabel
    Request Method:POST
    Status Code:400
    Referrer Policy:no-referrer-when-downgrade

    “[0] Could not load file or assembly ‘MDYMOBarcode.dll’ or one of its dependencies. The specified module could not be found. [1] Exception has been thrown by the target of an invocation. [2] There is an error in XML document (28, 4). [3] There is an error in XML document (28, 4). [4] There is an error in XML document (28, 4). [5] Unable to load label template “

    • back to DLS8Setup.8.5.4 with the https error. :-(

    • Have you looked in C:\Program Files (x86)\DYMO\DYMO Label Software?

    • Hi,

      We have seen this in the past with one of our other products and problem had something to do with the client’s Windows installation. After reinstalling Windows and our application everything worked again.

      I understand that may be a bit extreme for you so please try the following first:

      1. Download and install SysInternals Process Monitor:

      2. Run it prior to starting your application.

      3. Add a “Path” filter that contains “MDYMOBarcode.dll” and then apply it before pressing OK.

      4. Look at the various entries to see if it manages to find the DLL in the directory where you installed it. If not, please report back the failure results.

      When I ran this I could see that the MDYMOBarcode.dll was successfully found. Hopefully you will be able to determine from this why it isn’t being found for you. Perhaps you installed it under a different user account with different permissions?

      Here is an example of my output:

      This may also be of help:


 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>