Exit / Quit everything.
Manually back up your Bookmarks - use the Brave Browser Bookmarks Manager to export - thus creating a “bookmarks . . .html” file – and place that file in a directory, other than in the BraveSoftware folder path.
And, back up your BraveSoftware folder:
Windows OS:
%LOCALAPPDATA%\BraveSoftware\Brave-Browser\User Data\Default\
–
When ready . . .
Use Microsoft Edge and go to:
https://www.avg.com/en/signal/proxy-server-definition
Scroll down to “How to find your proxy server address in Windows” . . . and double-check, to see if your Windows OS machine is using a Proxy Server.
Note: After following those steps, also use a Brave Browser > New Window, and go to: brave://settings/?search=proxy . . . and double-check, that method of going to your computer’s Proxy Settings.
–
Next, using a Brave Browser > New Window - go to brave://settings/security
Disable: Use secure DNS
–
Next, using the Brave Browser > New Window, go to: brave://settings/cookies
Disable: Clear cookies and site data when you close all windows
–
Next, using the Brave Browser > New Window - go to brave://settings/clearBrowserData . . . and select the Clear browsing data > Basic tab.
Enable all 3 selections and click the “Clear data” button
–
Return to: brave://settings/clearBrowserData
For tab On Exit
- Disable:
Passwords and other sign-in data - Disable:
Site and Shields Settings
Click on the “Save” button.
–
Double-check the DNS server numbers that you are using for your Windows OS machine’s connection to the Internet:
https://www.windowscentral.com/how-change-your-pcs-dns-settings-windows-10
Free and Public DNS Servers:
https://www.lifewire.com/free-and-public-dns-servers-2626062
–
Next, in a Brave Browser > New Window, go to brave://net-internals/#dns and click on “Clear host cache”
Enter another Brave URL brave://net-internals/#sockets and click on “Close idle sockets” . . . and then click on “Flush socket pools”
Exit / Quit Brave Browser
Exit / Quit everything else and Restart your Windows OS machine.
–
Notes re what are:
DNS cache:
Socket pool:
With pooling, instead of closing a connection after it is used, we can keep it idle while it waits to handle another request. This saves the resources required to create a new connection.
- Ref. : ‘https://betterprogramming.pub/build-a-tcp-connection-pool-from-scratch-with-go-d7747023fe14’
–
Very easy, plain website that simply displays DNS status:
https://test.nextdns.io
–