HSTS Does Not Stop You Using a SOCKS Proxy
Distinguish a SOCKS connection failure from HSTS enforcement and HTTPS certificate validation.
HSTS does not require a direct connection. HTTPS can run through SOCKS with its normal TLS and certificate verification; HSTS tells the browser to use HTTPS for the host and strictly handle certificate failures.
If the browser reports a SOCKS connection failure, first check the selected SOCKS version, the proxy's ability to reach the destination HTTPS port and where destination DNS is resolved. A failed negotiation or refused destination connection happens before the website certificate can be assessed.
A certificate error after the connection opens is a different stage. HSTS can prevent bypassing that error, but it did not cause the earlier SOCKS negotiation to fail. Compare the website hostname and trust chain rather than disable HTTPS policy to compensate for a transport problem.
SOCKS itself does not turn the path into TLS interception. An untrusted proxy can drop or misroute traffic, while valid end-to-end TLS is intended to detect impersonation. Installing a new root certificate changes that trust arrangement and is not a routine fix for HSTS. When one site works and another fails, compare their actual connection stages and destination requirements. For an allowed comparison through a public endpoint, the SOCKS proxy list provides candidates; match the version and authentication support to the browser.