brave-browser: Single websocket won't connect using brave. Works for all other browsers.
Similar issue here: https://github.com/brave/brave-browser/issues/22851
But apparently fixed.
Description
After multiple refreshes of our app: https://endx.gg, the websockets stop connecting.
Chrome works as expected, as does wscat.
E.g. wscat -c “wss://auth.endx.gg/api/prices”
Steps to Reproduce
- Head to endx.gg
- Sign in with test@test.com
- Password: Testing1!
- Shields can be up or down
- Refresh the browser multiple times (keep refreshing until it happens)
- Websockets stop connecting
Actual result:
Expected result:
On chrome:
Reproduces how often:
All the time.
Brave version (brave://version info)
Version 1.40.107 Chromium: 103.0.5060.53 (Official Build) (arm64)
Brave | 1.40.107 Chromium: 103.0.5060.53 (Official Build) (arm64)
-- | --
Revision | a1711811edd74ff1cf2150f36ffa3b0dae40b17f-refs/branch-heads/5060@{#853}
OS | macOS Version 12.4 (Build 21F79)
JavaScript | V8 10.3.174.14
User agent | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.53 Safari/537.36
Command Line | /Applications/Brave Browser.app/Contents/MacOS/Brave Browser --disable-client-side-phishing-detection --disable-domain-reliability --enable-dom-distiller --no-pings --component-updater=url-source=https://go-updater.brave.com/extensions --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --flag-switches-begin --flag-switches-end
Executable Path | /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path | /Users/mark/Library/Application Support/BraveSoftware/Brave-Browser/Profile 1
Linker | lld
Active variations | AdRewardsStudy:NextPaymentDayAdServingStudy:DefaultAdNotificationsPerHour=10/MaximumAdNotificationsPerDay=100/MaximumInlineContentAdsPerHour=12/MaximumInlineContentAdsPerDay=60BraveAds.EpsilonGreedyBanditStudy:ControlBraveAds.FrequencyCappingStudy:ExcludeAdIfWithinTimeWindow=0hBraveAds.UserActivityStudy:Triggers=EMPTY/Threshold=0.0/IdleTimeThreshold=5BraveDebounceStudy:EnabledConversionsStudy:NewDefaultPatternDefault1pBlockingStudy:DisabledDisableReduceLanguage:DefaultEphemeralStorageStudy:EnabledExtendedVariationsSafeMode5:SignalAndWriteViaFileUtil5FirstPartyEphemeralDomainBlockStudy:EnabledForceDisableBlinkFeatures:EnabledMacCoreLocationBackendStudy:EnabledNativeCosmeticFilteringStudy:EnabledPartitionBlinkMemoryCacheStudy:EnabledPartitionConnectionsByNetworkIsolationKeyStudy:EnabledPermissionLifetimeReleaseStudy:EnabledRequestAdsEnabledApiStudy:EnabledSpeedreaderReleaseStudy:Enabled
Version/Channel Information:
- Can you reproduce this issue with the current release? yes
- Can you reproduce this issue with the beta channel? not tried
- Can you reproduce this issue with the nightly channel? not tried
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? no
- Does the issue resolve itself when disabling Brave Rewards? no
- Is the issue reproducible on the latest version of Chrome? no
Miscellaneous Information:
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15
Same here.
Need to disable Trackers & ads blocking:
I am a little bit disappointed
(EDIT: I calibrated my language to not appear pretentious)
There should be some flag “allow dev mode” to connect to localhost.
(apparently someone in the past abused it to fingerprint / track users)
I’ve heard about Brave since 2017 and BAT, and here we are in 2023, in the meanwhile tried many times to switch and each time I found some “non starter” issue in the first 5-10 minutes of usage.
Related: https://github.com/danhper/atomic-chrome/issues/36
I have the same issue. I am working on the backend based on Nest.js. I have WebSocket that all other browsers will work fine but the brave browser was working fine after a while it won’t receive messages from a WebSocket. note that my operating system is Windows 10 in case you want to change the issue tag.