Re: Large stderr.log with bad_certificate(42) errors
The easiest way to fix that is to run IISCrypto on both epo and sql servers, choose best practices (you can disable tls 1.0 if desired), then reboot. That should resolve those errors. Once you do that, check the server log for any failed to send http request errors for after the reboot. Hopefully there should be none.
Was my reply helpful? If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.