windows 11 SSL

asked on October 27, 2021

I've figured out the answer to this prior to posting, but wanted to help others since support's response was "Windows 11 is not supported." I upgraded to Windows 11 and the web products (which were using SSL) stopped working. It is a SSL issue rather than an issue with the products themselves. If you go to https://localhost, you should get the iis screen, but in the case you get the same SSL error.

Fix: Windows 10 certificates (at least self-signed ones) do not work with Windows 11. You need to create a new one, then go to SSL bindings and change it there, and go into the XMLEndpointConfiguration deleting the binding and configuring the new binding from the dropdown. At that point everything should work again.

0 0

replied on October 27, 2021

There's not enough information to guess, but it doesn't sound like a Laserfiche issue. Was the certificate no longer valid?

0 0

replied on October 27, 2021 • Show version history

Certificate was renewed last week and working as of yesterday. You are right that this is a Windows issue, probably a bug (there's already a patch out today so maybe MS is on it), but it affects Laserfiche. In 14 years, I've installed LF web products on a non server version of Windows maybe a half dozen times so it likely won't be a wide spread issue, but it is an issue for those running SSL locally and for VARs running the VAR kit locally on their machines. I simply wanted to provide a solution to those that do encounter it.

0 0

replied on October 28, 2021

Thanks for letting us know. Our testing focused on clean installs of Windows 11, not machines upgraded from previous versions of Windows.

Windows 10 upgrades have accidentally cleared out certificate stores in the past, so it is possible you were seeing something similar when upgrading from Windows 10 to 11. My question was trying to narrow down what you were seeing (certificate invalid, missing or some other symptom).

0 0

replied on November 4, 2021

The only error I found was when I hit F12 on the form. That's where it said the certificate was invalid. The certificate was still in the certificate store, seemed to be correctly bound and had the correct expiration date (next year). I honesty don't know enough about certificates to have tried to fix the existing one so I tried creating a new one and made the necessary binding and LF configuration changes and it worked.

0 0

Question

Question

Replies

Sign in to reply to this post.