I am still running version 2 of DEVONthink (on macos 10.12 Sierra), so I’m not expecting any action, just clarification.
As of a week or so ago (between August 11-13), I am unable to clip to markdown. When I attempt to do so, I end up with a bookmark. I saw some posts on a similar matter but this seems different.
I have tried with Firefox and an old version of Opera and I get the same results
I have tried with unclutter enabled and disabled, with the same results
I have created Formatted Notes, both cluttered and uncluttered, without issue
So the issue I am facing is specifically with the markdown type.
I use the Clip to Devonthink addon to trigger it.
For what it’s worth, my computer seems to be connecting to the tool URL but there isn’t the response I’m hoping for.
Any ideas? Please let me know if you require any further information.
This happens quite a lot of the time in later versions of DT as well, as the automatic fallback when clipping to Markdown isn’t able to process the page for whatever reason. It’s nearly always resoluble in later versions by running Data => Convert => to Markdown on the bookmark, though I don’t know whether that exists in DT 2.
I think it could be related to the new certificate, like here:
Safari still doesn’t accept the certificate as valid for me. (I haven’t tried manually installing the certificate like @FrodeW yet).
I can’t get markdown clipping to work no matter how many times I try. It usually works on the second try when the first one fails, but now I just get markdown document containing only a metadata header with title and description.
I have been experimenting with clipping articles as markdown in other ways, so I hadn’t noticed how consistent the behaviour is and connected the dots before today.
I’m on 15.6. I guess that’s the reason. The intermediate and/or root certificates of Sectigo probably have arrived in the keychain somewhere between 13.7.7 and 15.6.
The Sectigo certificates are available here:
I don’t know which ones you really need, though. Short of downloading and installing them (and perhaps even granting trust manually) or upgrading to 15x, I don’t see a lot of ways to solve the issue.
The Root certificate is valid since 2021-03-21. That is more than a year before Ventura (macOS 13) was published. But it is not part of the trusted roots installed with that version:
macOS 14.4 includes it:
Background: DEVONtechnologies bought their SSL certificate from Sectigo. Which is ok, given that they are generally accepted as a trustworthy CA. Or maybe not so generally, because their root and intermediate certificates are not available in your macOS version.
Thank you! I know absolutely nothing about certificates, so I had no idea some (or all?) root certificates were installed by/with the operating system.
BLUEFROG mentioned in the other thread that they were trying to figure out why some users had problems and others not. Since it wasn’t a pressing issue for me I just decided to wait a bit.
If the root certificate is not installed with macOS 13, it most definitely isn’t installed with the macOS 10.12 OP is using.
Firefox never reported a problem, but I guess it doesn’t rely on Keychain.app
Successfully enough that I’ve never needed to fiddle with it
I wasn’t sure what to download from your link, so first I tried downloading the SectigoPublicServerAuthenticationRootR46_USERTrust.crt linked here:
I simply double-clicked to open it in Keychain.app. That was all it took to install. Now Safari trusts the certificate, the support assistant has its content back – and DT’s markdown clipper works again.
Good to hear that you got it fixed, too. It is indeed that simple. The only way it can fail is if you have selected the wrong keychain, such as the System keychains, where you need to be root to install certificates. As long as you choose the login keychain, the installation is automatic by simply double-clicking the certificate file.
Thank you all for investigating with us! We have just published a post recommending this as the solution in case of connection problems to our sites and services.
We have just published a post recommending this as the solution in case of connection problems to our sites and services.