Error 500 After TLS 1.2 Guide
Hi,
I got an Error 500 After enableing the TLS 1.2, by provided guide.
And the error stays even after disabeling TLS 1.2.
/connect, /remote, ALL sites give Error 500.
even http%servername% (usuallt gives an IIS Basic welcome page)
I did the asked reboot after the Enabkeing and Disabeling of the server.
Funny thing is, Client Backup still functions ok, and Folder are still ocupied with files (asuming they work)
Is there an step by step control sheet of what edits this software makes?
or can someone provide me the basic settings of the IIS server and folder?
Guide:
Enabling TLS 1.2 On Windows Server Essentials
Reinstall isnt an option on a running DC with Clients
- MOHdennisNL asked 2 years ago
- last edited 2 years ago
- You must log in to post comments.
Im also sorry for having issues with the RemoteApp software.
its fairly sure that during the disabeling of the TLS 1.2 specs, the software broke a few IIS options.
I just found out that:
using %servername%
%servername%/Connect
BOTH give an 500 error,
While
%IPaddress%
%IPaddress%/Connect
BOTH are working (showing/displaying atleast)
I dont have a client to retest the working of the connector software.
=============================================
probably 1 of the bugs is, when you ‘disable’ HSTS, the option of actually disabeling wont work.
The 2 greyed-out boxes are indeed ACTIVE on:
IIS > Default Website > Action section > Advanced Settings > HSTS tab
=============================================
The only issue now is why does the IIS only work on IP level?
where did the ServerName go to?
- MOHdennisNL answered 2 years ago
- just notiched on the Clients, ALL traffic to IIS is being Redirected with HTTPS. RDWeb is Accessible All others give an Error 500
- I just fixed the HTTPS redirect error. https://galaxyinternet.us/google-chrome-redirects-localhost-to-https-fix/#:~:text=When%20Google%20Chrome%20keeps%20redirecting%20your%20localhost%20Url,panel%20%28CTRL%2BSHIFT%2BI%29%20Click%20and%20hold%20the%20reload%20icon It seems to be an Chrome/Cache issue. Disclaimer: I did NOT test Your connect software on functioning. So again, if you can/WILL give me the basic settings made in IIS. This way we can make an default fail-safe for Future Issues.
- You must log in to post comments.
Alas, I have no idea what could be going on there seeing as I’m not able to replicate that issue over here on any of our in-house test servers (i.e. the feature works just fine for us here, and to date, no one else has reported a similar issue/error that I am aware of). As for exactly what the feature does… It simply runs the following script on the server (and unrolls it when you tun the feature off again):
Setup Microsoft Windows or IIS for SSL Perfect Forward Secrecy and TLS 1.2
If you opt to disable TLS 1.0 as well, then that is also performed via the above script, and the “SchUseStrongCrypto” and “SystemDefaultTlsVersions” settings are added to the registry as per Microsoft’s guidelines here:
Transport Layer Security (TLS) best practices with the .NET Framework
Sorry that I don’t have a better answer for you on this one.
- Mike answered 2 years ago
- You must log in to post comments.
