"None of the ports were configured to use SSL certificate" - Dymo Web Service

gistfile1.txt

I can't describe how much I hate Dymo developers. Long hours of annoyance were caused by their negligence.

So you are here, because you are looking for solution for "None of the ports were configured to use SSL certificate" 

- when you try to diagnose Dymo Web Service.

The good developers at Dymo forgot to delete/check/reinstall (call as you want) certificates when you uninstall/reinstall the web service.

After hours (days!) I found the solution.

$netsh http show sslcert

You can see that there are ports for Dymo configured... these should be deleted when you do an uninstall. Instead of this,
Dymo installer is just ignoring and doesn't reinstall the certificates -> you can never launch the web service.

So what to do?

Uninstall Dymo Label software.

Launch terminal with admin rights.

$netsh http delete sslcert 127.0.0.1:41951
$netsh http delete sslcert 127.0.0.1:41952
...
$netsh http delete sslcert 127.0.0.1:41960

If you are done, install Dymo Label software (it takes longer as usual) and voila. Everything works as it should.

Click the star if this helped you.

Thanks.

I was so happy to find this, because I think I am having this exact problem.

But when I type $netsh http show sslcert
I get: zsh: command not found: http

I don't know how to use the command line tools well enough to know what I'm doing wrong. Any chance you can point me in the right direction?

Zsh? Are you on linux?

I'm just using the MacOS terminal, which I think is a flavor of Linux but maybe I need to use a different shell or something? Sorry, I'm not a programmer, I'm just trying to get my label printer going again. Thanks for indulging me.

This guide is for Windows only.

Oops, I didn’t realize that the same problem existed under Windows. Interesting. Anyway, thanks for trying to help. On Dec 31, 2022, at 1:34 AM, adrianmihalko ***@***.***> wrote:Re: ***@***.*** commented on this gist.This guide is for Windows only.—Reply to this email directly, view it on GitHub or unsubscribe.You are receiving this email because you commented on the thread.Triage notifications on the go with GitHub Mobile for iOS or Android.