4 ms·
Assuming you use Google Chrome, you can start it with a few flags that make it ignore all SSL errors, this will be the "easier" solution than setting up a rever
by mmh0000 4y ago
Assuming you use Google Chrome, you can start it with a few flags that make it ignore all SSL errors, this will be the "easier" solution than setting up a reverse proxy.
chrome-wrapper --ignore-certificate-errors --test-type
Otherwise a reverse proxy like Apache, HAProxy, or nginx would work.
Now, instead of doing any of that, you should maybe try and figure out why you're having so many TLS issues where other people do not.
- forgotmypw17 4y agoI use at least 30 different browsers, Chrome being one of the least frequent. This helps, however. Thank you.
- forgotmypw17 4y agoI don't think I have an unusual amount of TLS issues per site browsed, I just browse many sites. For example, today wikiless.org's certificate is expired, and I cannot ignore the error in Waterfox because of HSTS, unless I "forget about this site", which removes all my History entries. I would estimate that I have about one issue per 100 sites browsed, which adds up.