On an ASP.NET Web api, I receive ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY issue after like every 2-3 months, which I resolve by going to IIS Crypto, clicking 'Best practices' and reboot.
I know that action disables all old protocols and ciphers, and best practices keep on changing in an effort to secure IIS. What I am after is a permanent solution to that problem. Will creating my own template selecting only a few cipher suites help?