Weirdly, I fixed this by switching to a different proxy protocol. If you’re using HTTP, try SOCKS5 (or vice versa). Chrome proxy settings can be picky.
Also, check `chrome://policy/` to see if your admin (or malware??) locked the proxy. If policies are enforced, you’ll need to remove them manually.
Last resort: Firefox. Just saying.
Also, check `chrome://policy/` to see if your admin (or malware??) locked the proxy. If policies are enforced, you’ll need to remove them manually.
Last resort: Firefox. Just saying.
