I use the site Wanderlog which is a travel itinerary planner.
I have had issues saving train travel on there and I contacted their support and they said it is a Brave issue.
It is whenever I try to add a train on my trip. It doesn’t save and 2 mins later it tells me to reload and I will lose my data. And I do.
You can replicate the issue by making a trip, then add a train. Wait a few mins and an error pops up saying there was a problem and you have to reload the page and you will lose the info you inputted.
It should just save and be done, but it just doesn’t save and the error appears a few mins later.
Their support said that it is related to webhooks and linked this saying it is the same issue but on their site too: https://github.com/brave/brave-browser/issues/23762
The issue was something that was supposed to have been fixed according to the post, but is still happening.
Their reply in full:
This is usually caused by network restrictions or if you are using the Brave browser. We have seen this issue with Brave and aren’t sure what causes it.
Brave seems to be blocking our WebSockets connections, but we’re not sure why. For now, I recommend just turning off any restrictions that might affect the WebSockets connections or just using another browser for the time being. My apologies for the inconvenience. This is actually a known issue not just to Wanderlog but for other websites as well.
Here’s a link for reference: https://github.com/brave/brave-browser/issues/23762 – hope this information helps!
So they are blaming this issue for it and say they don’t know why but it’s happening and that was all they were able to offer about the issue and just told me to use Chrome which I won’t do.
When I asked if they were trying to fix it they said they don’t know why it is doing it, so basically no they aren’t.
Main issue is that the issue they are blaming is something that was supposed to have been fixed, but isn’t fixed at all.
Read that other thread on Github for info.
Wanderlog say it’s been going on months so they know about it but just aren’t working on it as they don’t know why.
I even suggested they work with Brave but they just pointed me back to the Github post which hasn’t been updated since May and doesn’t mention it is happening on Wanderlog too as Wanderlog didn’t even reply to it to say it’s happening on their site too.
I have the latest version of Brave, but it happened with the last 2 versions too.
I am on Version 1.57.49 Chromium: 116.0.5845.96 (Official Build) (64-bit)