Grant.rewards.brave.com refused to connect

Brave Rewards Rewards Support
1

I posted here and Chris had me send a log, but I’ve never heard anything back. Still not working. I am not the only one with this issue either.

https://www.reddit.com/r/brave_browser/comments/z5mfmg/solve_for_rewards_not_working/

And here’s another guy with same issue.

2 Likes
2

The team is looking into this. Thank you.

1 Like
3

@zmaint No, you are not the only one with this issue, there are at least two others that have reported it, including myself. Hopefully it will be resolved soon and it will not affect brave rewards

1 Like
4

Thank you, hopefully this will be corrected soon.

1 Like
5

Same error here. I’m using Linux. No VPN, no Firewall.

6

Same here. Fedora 36 connecting from Brazil

7

Same here.
In the UK, PopOS (Linux), no VPN enabled.

1 Like
8

I’m having the same issue on my Steam Deck desktop mode after the recent update.

1 Like
9

Another steam deck user here. Same problem. SteamOS(arch linux)

10

Interesting update. My laptop, same Linux distro and Brave version, has been working fine… until today. Now Brave is doing the same thing on it. I have not updated anything since the original post. All info matches my desktop.

11

Just updated my system. New Brave version is 1.46.133 Chomium: 108.0.5359.71 (Official build)

On first launch, Brave rewards asked me for my country. I selected it (United States) and then was met with the old familar error:
grant.rewards.brave.com refused to connect.

So… still not working.

1 Like
12

Same error here…using Linux.

  • No VPN
  • UFW Firewall on or off…

grant.rewards.brave.com refused to connect.

13

Everyone, please see the following GitHub issue.

  1. There’s a temporary workaround. Instructions in the GitHub issue (see comments).
  2. There’s almost certainly an issue if Flatpak, as numerous users have reported this, and we’ve also reproduced it.

“Flatpaks and Snaps have extra sandboxing that sometimes breaks features”

1 Like
14

Brave is in my repo (not a flatpak or snap).

I tried the hacky workaround. Here’s the error when I try to relaunch the captcha in a new window:

{“message”:“Failed to create Captcha for payment ID "f474894e-24eb-4b01-8935-8af819324f2b": Error retrieving scheduled captcha ID: Unsolved captcha not scheduled”,“code”:500}

Also fun story. Yesterday once out of the very many times I used Brave, under the solve option was the option for 'later". I clicked it and everything worked fine. But on next launch of the browser it was back to the same error again.

I just tried this on my desktop, same distro, same version of Brave and it seems to have worked… at least for now. Very odd.

1 Like
15

Having the same issue on Steam Deck running SteamOS 3.3.2 , KDE Plasma 5.23.5.

16

Updated to 1.46.138 Chromium 108.0.5359.94 on my laptop on Friday. So far the issue appears to be gone.

1 Like
17

Hey you there… Today I was able to solve the puzzle :rofl: :rofl: :rofl:
Version 1.46.144 Chromium: 108.0.5359.128 (Official Build)
Fedora 36 / Gnome / From Brazil / No VPN / No Proxy

Peace!

18

I’ve had no more issues on either desktop or laptop after updating to the version I mentioned above, 1.46.138 Chromium 108.0.5359.94.

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.