@rachid Hi 
Did you try the troubleshooting steps in the Chromium link? Reposting link.
https://www.chromium.org/developers/design-documents/network-stack/socks-proxy/
Debugging
There are a lot of intricacies to configuring proxy settings as you intend:
- Different profiles can use different proxy settings
- Extensions can modify the proxy settings
- If using the system setting, other applications can change them, and there can be per-connection settings.
- The proxy settings might include fallbacks to other proxies, or direct connections
- Plugins (for instance Flash and Java applets) can bypass the Chrome proxy settings alltogether
- Other third-party components in Chrome might issue DNS resolves directly, or bypass Chrome’s proxy settings.
- The first thing to check when debugging is look at the Proxy tab on about:net-internals, and verify what the effective proxy settings are:
chrome://net-internals/#proxy
Next, take a look at the DNS tab of about:net-internals to make sure Chrome isn’t issuing local DNS resolves:
chrome://net-internals/#dns
Next, to trace the proxy logic for individual requests in Chrome take a look at the Events tab of about:net-internals:
chrome://net-internals/#events
Also posting a link to clearing DNS cache that may be helpful.
Really, those troubleshooting steps will help narrow down/eliminate problems. You should work through all of those, especially clearing history/caches, disabling extensions, and creating a new profile to see if works in a new profile. You should probably try to see if you still have a problem using Brave Beta and/or Nightly releases.
If you are still experiencing an issue after troubleshooting, please post an update and provide any new information. Please provide your Brave and OS versions found at brave://version too. Tag the moderators in your update post. The moderators may have additional information or troubleshooting steps. They will need the troubleshooting information and your Brave/OS version to provide additional support.