Dymo Connect Service 1.4.3.103 (Mac) SecureChannelFailure

[andlitvak]

Attempting to resolve printing issues caused by Chrome 98 on Macs, we tested Dymo Connect 1.4.3.98 Beta by using the instructions provided here.

We then reviewed the Dymo website and downloaded the most up to date version of Connect for Mac and found it was version 1.4.3.103. I completely removed the Beta from my computer and installed 1.4.3.103. The issue is that the Dymo Connect Service for Mac has an error when using the 'Diagnose' function.

I've attached the Log File created via the Dymo Connect Support Tool for mac as well.

log_20220302.txt

I've tried uninstalling and reinstalling multiple times (restarting between each step) with no results. The one thing that did work was to do a clean install of the 1.4.3.98 Beta and then install 1.4.3.103 on top of it without removing anything. This seemed to rectify the issue. Obviously we can't recommend this to our customers so any help @dymosoftware would be really appreciated.

[andlitvak]

A Bit more detail pulled from the Log File. I believe that the issue is logged here

3/2/2022 7:21:22 PM|Exception System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode () [0x0001b] in /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/src/Xamarin.Mac/external/corefx/src/System.Net.Http/src/System/Net/Http/HttpResponseMessage.cs:168 at System.Net.Http.HttpClient.GetStringAsyncCore (System.Threading.Tasks.Task`1[TResult] getTask) [0x00096] in /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/src/Xamarin.Mac/external/corefx/src/System.Net.Http/src/System/Net/Http/HttpClient.cs:150 at DYMO.DCDesktop.Misc.UpdateHelper.CheckForUpdates () [0x00118] in /Users/buildsystem/TeamCity/DCDBuild_Hansel/DCDesktop/DYMO.DCDesktop/Misc/Updates/UpdateHelper.cs:66 Callers: /Users/buildsystem/TeamCity/DCDBuild_Hansel/DCDesktop/DYMO.DCDesktop/Misc/Updates/UpdateHelper.cs, CheckForUpdates, 72,

When I install the Beta Package and use the Upgrade flow built into connect everything appears to work. So there appears to be an issue with the 1.4.3.103 file being distributed on the Dymo website.

[systemx-xx]

sudo kill $(ps -e | grep "DYMO" | grep -v grep | awk '{print $1}') sudo rm -rf /Library/Frameworks/DYMO sudo rm -rf /Library/Printers/DYMO sudo rm -rf /Library/Extensions/DymoUsbPrinterClassDriver.kext sudo rm -rf /Library/LaunchAgents/com.dymo. sudo rm -rf /Library/LaunchDaemons/com.dymo. sudo security delete-certificate -c "localhost" sudo security delete-certificate -c "DYMO Root CA (for localhost)" sudo rm -rf /Applications/DYMO*

Then Install 1.4.3.103

[andlitvak]

Thanks @systemx-xx . I did some additional testing on computers that have NEVER had any dymo software installed, and they ran into the same issue. @dymosoftware Would appreciate any additional recommendations

[BillDuggin]

I confirmed that ALL previous DYMO packages, libraries and certificates were uninstalled, then installed the latest DYMO for Mac (version 1.4.3.103), but also getting the "SecureChannelFailure..." error message when selecting Diagnose from the menu.

[dymosoftware]

DCD 1.4.3 web service will be conflict with DLS web service as of current Release version which we found recently. If you installed DLS app, then please uninstall DLS app from DLS installation dmg file. One of the step of installation is able to drill down to Installation Type and then you can select uninstall. And then you can follow the installation step to solve the issue as following link. https://github.com/dymosoftware/Beta-Version/issues/2#issuecomment-1043410792

[andlitvak]

So testing and still finding issues

1. I used the DMG files for Label and Connect to fully remove both from my computer. I then installed 1.4.3.103 (from the Dymo website - not beta build) and received this error.

2. Used the Uninstaller of connect and then followed instructions here. I then downloaded a fresh copy of 1.4.3.103 dmg from Dymo website. After installation, the installer prompted me for my Password via Terminal (something that I would hope is not intended functionality as our end users would find this odd) . This finally did allow me to use Dymo Connect 1.4.3.103 Service

@dymosoftware Is there a release date for an update of Dymo Connect for mac that allows users to run the web service without going through their root folders or needing to understand how to use terminal? We have an integration that is scheduled to go live on 3/30 and this is vital to that plan. Any additional info would be incredibly helpful to us. Thanks so much!

[dymosoftware]

We are going to find the better seamless solution, however it will take time.

[andlitvak]

Thanks @dymosoftware Is there any current projection of when that update might be released?

[andlitvak]

@dymosoftware Any updates you can share?

[sprousecu]

I've tried all of the steps provided by others (systemx-xx and andlitvak) to install Dymo Connect 1.4.3.103 on a brand new mac-mini 12.3 (Monterey) times now... to no avail. I always end up with the same failed diagnostics message.

UPDATE! Finally some success with 1.4.3.103. The first few tries I did not see a localhost file in Keychain Access. Only after I did a find, Ctl F, did it show up. You must click on it to see that it is associated with DYMO. Then, after removing it (and using the Dymo Install pkg to uninstall) the DMO diagnostics was successful. For my companies application, which runs in Chrome, I also had to use the developer tools to empty the cache and perform a hard reload. (launch developer tools, then right-click the refresh icon and select 'empty cache and hard reload'.

This is a very convoluted process so I do hope there is a cleaner process coming soon, one without the need for terminal.

[andlitvak]

@dymosoftware Just following up on this. ANY updates would be greatly appreciated

[andlitvak]

@dymosoftware Any chance we could get an update on this please? Sorry for being a bother, but this update is somewhat mission critical for our 5,000 users.

[sprousecu]

Though I have tried multiple times on both older Intel processors running Catalina and the newer M1 Mac processors the fix that appears to work on machines that had DYMO label 8.7.5 installed requires all the steps andlitvak posted. For machines which had DYMO Connect 1.4.2 installed, the process can be a bit simpler because the DYMO Connect uninstall does a better job of removing most of its footprint. The one thing I had hoped was that I could simply just manually authorize the DYMO certificates, but that was not the case.

ATTACHED is a step-by-step guide that addresses both of these scenarios and hopefully provides a temporary fix for everyone while we wait for a realistic solution from DYMO. I hope to complete a video to accompany this post in the next day or two. Please let me know if this works, or does not work, for you situation

DYMO_Web_Services-MAC-OS_failure .pdf .

[andlitvak]

Thanks @sprousecu . I'm really keeping my fingers crossed for some update from @dymosoftware soon.

[katieswisher]

@dymosoftware My team is also waiting for an update on this. Anything to share?

[andlitvak]

@dymosoftware Just checking in on any timeline for an updated stable release

[andlitvak]

@dymosoftware Hey there - just wanted to check in. Any updates would be so helpful and appreciated. Thanks so much

[andlitvak]

@dymosoftware Been a while since the last update - Any news to share?

[jpivac]

ATTACHED is a step-by-step guide that addresses both of these scenarios and hopefully provides a temporary fix for everyone while we wait for a realistic solution from DYMO. I hope to complete a video to accompany this post in the next day or two. Please let me know if this works, or does not work, for you situation

DYMO_Web_Services-MAC-OS_failure .pdf .

Thankyou for this. Trusting the localhost certificate was the fix for a few of our clients.

[daniels]

I first wrote this in the wrong issue (#60) yesterday.

---

On MacOS Monterey. DYMO Connect Software 1.4.3.103.

After installation (using Homebrew cask) the "Diagnose..." menu item reports the error:

Error: SecureChannelFailure (Authentication failed, see inner exception.)

When visiting the status endpoint https://127.0.0.1:41951/DYMO/DLS/Printing/StatusConnected (the port may vary) it is not reported as a certificate error, but a protocol error. If I change the URL to http://127.0.0.1:41951/DYMO/DLS/Printing/StatusConnected it works. So it seems like my installation does not use an SSL certificate at all. (This is actually a good idea!)

But unfortunately the change is not reflected in the Javascript framework code. I checked the latest release, and it still sets WS_PROTOCOL to "https://".

I downloaded the framework file and changed this variable:

sed -i.bak -e 's/WS_PROTOCOL="https/WS_PROTOCOL="http/' dymo.connect.framework.js

Then my application could connect.

[apenab]

@dymosoftware any update here?

[hamzaafridi]

sudo kill $(ps -e | grep "DYMO" | grep -v grep | awk '{print $1}') sudo rm -rf /Library/Frameworks/DYMO sudo rm -rf /Library/Printers/DYMO sudo rm -rf /Library/Extensions/DymoUsbPrinterClassDriver.kext sudo rm -rf /Library/LaunchAgents/com.dymo. sudo rm -rf /Library/LaunchDaemons/com.dymo. sudo security delete-certificate -c "localhost" sudo security delete-certificate -c "DYMO Root CA (for localhost)" sudo rm -rf /Applications/DYMO*

Then Install 1.4.3.103

this worked for me

[ccc-developer]

Though I have tried multiple times on both older Intel processors running Catalina and the newer M1 Mac processors the fix that appears to work on machines that had DYMO label 8.7.5 installed requires all the steps andlitvak posted. For machines which had DYMO Connect 1.4.2 installed, the process can be a bit simpler because the DYMO Connect uninstall does a better job of removing most of its footprint. The one thing I had hoped was that I could simply just manually authorize the DYMO certificates, but that was not the case.

ATTACHED is a step-by-step guide that addresses both of these scenarios and hopefully provides a temporary fix for everyone while we wait for a realistic solution from DYMO. I hope to complete a video to accompany this post in the next day or two. Please let me know if this works, or does not work, for you situation

DYMO_Web_Services-MAC-OS_failure .pdf .

I just want to say that this step-by-step PDF guide DYMO_Web_Services-MAC-OS_failure .pdf helped me solve the Dymo Diagnose error: TrustError: TrustFailure (Authentication failed, see inner exception.). In particular it was Step 10 that solved my issue.

I would have never thought to check this Keychain certificate issue.

[DaviatorSF]

So I have been following the step-by-step guide in an attempt to solve this problem... but at the end of the installation, when the Terminal window opens, there are no commands executed there, no attempts to install the certificates. I just have the normal terminal prompt (no request for password.)

Is there a way to manually install the certificates?

I should note that there are no certificates found in Keychain Access when searching for Dymo, and only one localhost entry which is a private key unassociated, I think, with Dymo. So those certificates are not getting installed and I don't know how to make it happen.

Edit: I found a solution, though perhaps an inelegant one. I found a site which had an old version (1.4.2.69) of Dymo Connect available for download. I uninstalled the current version and installed this older version, and to my delight, discovered that it DID install the Dymo localhost certificate which was not installed by the current version. I then installed 1.4.3.103 over the older version. Success! The web service now passes the diagnostic and I'm able to print from the web service I want to use.

It seems as if 1.4.3.103's installer fails to install the necessary SSL certificate, and its absence was the entire cause of the problem I was having. This is a Dymo problem which I'm pretty surprised they've failed to fix in nearly a year.

[john2049]

@dymosoftware I see your last post approx. one year ago, any update for those of us who want/develop and need to use Dymo, I can go through the process above, but you had indicated that didn't fall within your own standards to have customers/clients do this. So I was curious in the last year what the resolution ended up bring?

[sprousecu]

@john2049 I provide support for clients of a product called RepairStorm, and as such I spent several days isolating the issues mentioned in my post and associated videos. That was really as a courtesy to members of this GitHub. I fully expected Dymo to address the issue themselves and come up with a firm solution within their software. As far as I know that has not happened, but I believe my "work-around" is still viable as RepairStorm clients, though there are few Mac users, have not reported any addittional issues.

[IDN-Tech]

After following all these guides on this forum nothing worked for me.

What I found to work without any sort of error is to download the Dymo Connect v1.4.2 software and install it normally under an administrator account on the computer. Even though the iMac was running the latest version of MacOS 13 Ventura v1.4.2 runs beautifully without issue. Detects my Dymo LabelWriter 550 and is able to print labels perfectly.

[rvill29009]

This is the simplest solution and it works. Thank you for investing your time trying all ideas.

[acollierr17]

sudo kill $(ps -e | grep "DYMO" | grep -v grep | awk '{print $1}') sudo rm -rf /Library/Frameworks/DYMO sudo rm -rf /Library/Printers/DYMO sudo rm -rf /Library/Extensions/DymoUsbPrinterClassDriver.kext sudo rm -rf /Library/LaunchAgents/com.dymo. sudo rm -rf /Library/LaunchDaemons/com.dymo. sudo security delete-certificate -c "localhost" sudo security delete-certificate -c "DYMO Root CA (for localhost)" sudo rm -rf /Applications/DYMO*

Then Install 1.4.3.103

I ended up doing a full clean install of Dymo, following the instructions, and installing the latest software. It resolved my issue, and I got a proper response when selecting "Diagnose" from the Dymo menu.

Thanks!

[nielspeen]

Following the official instructions to delete the certificate and re-install Dymo Connect did not yield any result.

Adding the commands provided by @systemx-xx that resolved the issue.

Why are these not incorporated in the installer?

[gitinbane]

sudo kill $(ps -e | grep "DYMO" | grep -v grep | awk '{print $1}') sudo rm -rf /Library/Frameworks/DYMO sudo rm -rf /Library/Printers/DYMO sudo rm -rf /Library/Extensions/DymoUsbPrinterClassDriver.kext sudo rm -rf /Library/LaunchAgents/com.dymo. sudo rm -rf /Library/LaunchDaemons/com.dymo. sudo security delete-certificate -c "localhost" sudo security delete-certificate -c "DYMO Root CA (for localhost)" sudo rm -rf /Applications/DYMO*

Then Install 1.4.3.103

It's October 2024 and this comment is the only thing keeping dymo alive.