search

dymosoftware / dymo-connect-framework

DYMO Connect Framework for Javascript.
Other
86 stars 54 forks source link

Dymo Connect Service for Windows tool SSL issue #60

Open joszil opened 2 years ago

joszil commented 2 years ago

We are using DYMO Connect V1.4.3.131 for windows and on some Windows 10 machines we are experiencing a SSL issue. When selecting the Diagnose menu item form the tool (hidden icon tray) we get following error:

"The SSL connection could not be established, see inner exception. Athentication failed because the remote party has closed the transport stream"

Tried several reinstalls, could this be a configuration issue? It is unclear what triggers this exception.

blester-mvc commented 2 years ago

I also have clients that have reported this issue but have not been able to figure it out. Hopefully @dymosoftware can provide some insight on this!

pbhogan commented 2 years ago

We're having the same issue. It seems to work if we run the app as administrator, but that's not ideal since we have lots of people with non-administrator accounts.

joszil commented 2 years ago

We're having the same issue. It seems to work if we run the app as administrator, but that's not ideal since we have lots of people with non-administrator accounts.

Which app should run as admin? The problem occurs in the DYMO Connect Service, should this service run as admin?

pbhogan commented 2 years ago

It's the DYMO WebAPI app (the tray app), not the DYMO Connect app. If you exit the app running in the tray, then find the application and run it as administrator, that bypassed the SSL error for us.

clevrdavid commented 2 years ago

This issue has been ongoing for quite a while now, we have users constantly seeking technical support for the software we provide, but the issue is actually with the Dymo Connect Service. It would be great if this could get some attention.

joeadcock commented 2 years ago

I am seeing this error on non-admin users on 1.4.3.131 for Windows, reverting to the previously installed version we were using (1.3.2.18) resolves the issue.

A work-around that appears to be working for v1.4.3.131 involves manually adding permissions to the Dymo localhost certificate:

  1. As an Admin, launch certmgr
  2. Navigate to the certificate at Personal > Certificates > localhost [issued by DYMO Root CA (for localhost)]
  3. Right-click, All Tasks > Manage Private Keys..
  4. Add "Authenticated Users" with Full Control and Read permissions (or the specific user(s) if you prefer)
  5. Click OK

Diagnose should now work for non-admin users as well on version 1.4.3.131!

Hopefully this feedback will also help the @dymosoftware resolve the issue within the install itself.

hixsepttt commented 2 years ago

I have same error SSL on Windows 1 - We uninstalled the dymo services 2 - Privilege elevation ( user -> admin) 3 - Installation of dymo connect 4 - Downgrade user (Admin ->user) its work now for simple user windows

clevrdavid commented 1 year ago

Are there any updates for this issue @dymosoftware? This is very frustrating. I have multiple clients constantly lodging support issues over Dymo printers not working with our applications and it is all down to Dymo Connect having issues when not installed under an administrator account. This never used to be an issue and DLS worked much much better. Can we please get some attention paid to this?

daniels commented 1 year ago

Edit: I realized that there was a separate issue for MacOS (#54). I have posted my comment there instead.

apenab commented 1 year ago

@dymosoftware any update here?

SimFre commented 1 year ago

@dymosoftware updates please? Also CORS, and perhaps an official Node module? :)

clevrdavid commented 1 year ago

@dymosoftware are you ever going to respond to this issue?

evan-orr commented 2 months ago

Issue appears to be resolved now, at least on version 1.4.5.1 of Dymo Connect. The DYMO Root CA is no longer under Personal in the certificate manager and is instead under the "Trusted Root Certification Authorities".