GFM online mode SSL/TLS secure channel aborts

dhenry 2018-02-25 19:59:08 UTC #1

Since mid-February 2018 this error has become persistent:

An error occurred while processing GitHub Flavored Markdown.
The request was aborted: Could not create SSL/TLS secure channel.
If the problem persists, please report the bug.

I seem to recall GitHub recently announcing that lower SSL/TLS security versions would no longer be supported. Might that be the issue? Does anyone have a solution?

jflottawa 2018-02-26 13:45:34 UTC #2

I'm having the same issue consistently. I tried switching to/from anonymous and it didn't help.

I (temporarily) switched to GFM offline

rev 2018-03-16 19:35:46 UTC #3

yes, github has deprected TLS 1.0 and 1.1. i just posted a duplicate of this topic; didn't realize it was already posted!

dhenry 2018-03-16 19:55:47 UTC #4

It'd be great if there was a simple tweak to cause the tool to use TLS 1.2. I'm not smart enough to figure out how.

Pauwris 2018-03-17 18:10:49 UTC #5

I hope this will be fixed soon, the Offline mode doesn't support the code syntax coloring.
I'm using Markdownpad2 Pro on nearly daily basis

dhenry 2018-03-18 23:50:34 UTC #6

Another disappointment is that offline mode leaves comments intact in the HTML output, whereas online mode stripped them.

kingkeith 2018-03-28 09:32:22 UTC #7

my understanding is that MDP2 is built with .NET Framework v4.0, which doesn't support TLS 1.2 or use it by default.

but if you have .NET Framework 4.5 installed, you can update some registry settings and restart MDP2 and GitHub Flavoured Markdown Online starts working again

dhenry 2018-03-29 22:49:40 UTC #8

Thanks much! I had somehow managed on my own to stumble my way to performing the changes described in step 1 awhile back. No joy then and so had posted the topic here. Your providing the URL to where the additional step 2 is described is what did the trick. Much joy now! Thanks a bunch.

Pauwris 2018-04-18 11:11:11 UTC #9

Thanks a lot kingkeith, that worked for me!

thofsommer 2018-09-24 18:26:09 UTC #10

This was the specific set of registry changes I needed to make on my Windows 10 machine to get it working with GitHub GFM:

FixDotNET.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001