Notification Ads not appearing, HTTP 426 errors in rewards-internals logs

[Finster]

*Briefly describe your issue:
Rewards are enabled and all ads are enabled, including notification ads. Notification ads never ever fire. All other ads work as expected.

What Operating System and Brave version are you using (Menu --> About Brave)?
Nobara Linux 38 (based on Fedora)
Brave version 1.60.118 Chromium: 119.0.6045.163 (Official Build) unknown (64-bit)

Is your Brave Rewards Profile currently verified? (yes/no)
yes

What date did you connect a your Brave Rewards Profile?
uhh… 11/20/23, I think?

Have you been able to successfully receive payments in the past?
no payments received yet, but I think that’s normal since I just joined

Are you using a VPN? (yes/no)
no

Are you in a supported region (see here for list of supported regions)?
yes

Does your device pass the SafteyNet check (Android only)?
not android

I should point out that this worked like a dream on my Windows 11 install. I have just recently installed this linux distro on my desktop, though, and have never gotten a notification ad. Other things I’ve tried:

1. tested notification at https://www.bennish.net/web-notifications.html, everything there works.
2. Notifications from other apps work
3. Browser is not listed in Notifications settings, but as tested above, this doesn’t seem necessary on this flavor of linux, as other apps also not listed in OS settings work as well (like Discord)
4. Disabled notification ads, deleted client.json, restarted browser, re-enabled ads, restarted browser (so it re-creates client.json) and still no notification ads.
5. Checked https://sampson.codes/brave/ads/my_region/, there is an issue with this site. When I first load the site, nothing loads at all. When I refresh I see tons of campaigns for my region (30 campaigns and 406 creatives). Subsequent loads seem ok.
6. enabled the flag brave://flags/#brave-ads-custom-push-notifications-ads
7. Checking brave://rewards-internals, the logs have a ton of errors:

--------------------------------------------------------------------------------
[Nov 23, 2023, 9:34:40.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 23, 2023, 9:34:41.2 PM:ERROR:refill_confirmation_tokens.cc(188)] Failed to get signed tokens
[Nov 23, 2023, 9:36:03.9 PM:ERROR:refill_confirmation_tokens.cc(188)] Failed to get signed tokens
[Nov 23, 2023, 9:47:25.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 23, 2023, 9:57:26.5 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 23, 2023, 10:05:50.8 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 10:55:34.0 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 23, 2023, 10:57:32.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 10:57:32.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 10:57:43.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 10:59:48.9 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:00:30.6 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:06:59.8 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
--------------------------------------------------------------------------------
[Nov 23, 2023, 11:16:00.6 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:30:20.1 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:30:20.1 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:34:33.1 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:35:31.2 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:38:24.7 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:38:24.7 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:52:47.1 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 23, 2023, 11:54:59.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
--------------------------------------------------------------------------------
[Nov 24, 2023, 6:28:30.1 AM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 6:44:55.9 AM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 6:45:22.8 AM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 6:45:42.4 AM:ERROR:publisher.cc(625)] Publisher info not found
--------------------------------------------------------------------------------
[Nov 24, 2023, 4:32:49.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
--------------------------------------------------------------------------------
[Nov 24, 2023, 4:50:59.5 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 5:16:24.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 5:16:47.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 5:17:30.7 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 5:17:30.7 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 5:32:20.7 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 5:51:48.4 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 5:55:00.0 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 5:55:41.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 6:08:37.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 6:13:53.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 6:18:54.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 6:18:54.4 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 6:30:50.1 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
--------------------------------------------------------------------------------
[Nov 24, 2023, 7:01:27.9 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 7:11:56.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 7:22:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 7:32:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 7:43:26.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 7:53:56.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:04:26.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:14:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:25:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:35:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:46:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 8:56:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:07:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:17:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:28:26.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:38:56.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:49:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 9:59:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 10:10:26.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 10:20:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 10:31:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 10:41:56.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 10:52:26.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 11:02:56.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 11:13:26.3 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 11:23:56.2 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 11:34:40.1 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 24, 2023, 11:36:13.2 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 11:36:13.2 PM:ERROR:publisher.cc(625)] Publisher info not found
[Nov 24, 2023, 11:36:13.2 PM:ERROR:publisher.cc(625)] Publisher info not found
--------------------------------------------------------------------------------
[Nov 24, 2023, 11:48:22.1 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
--------------------------------------------------------------------------------
[Nov 24, 2023, 11:58:39.9 PM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426
[Nov 25, 2023, 12:08:40.1 AM:ERROR:get_available.cc(63)] Unexpected HTTP status: 426

Not sure what else to check at this point.

[RobertT]

*Briefly describe your issue:

Same errors++.

Even after I reset my Brave Rewards profile twice, I still get the same problem.

I emailed support both times I reset my Brave Rewards profiles but they kept sending me the same message that my profile had been flagged for irregular activity and it won’t be reinstated, which was strange because these were new profiles and I haven’t done anything irregular on either my new profiles or even on my original one.

What Operating System and Brave version are you using (Menu --> About Brave)?

macOS Ventura

Is your Brave Rewards Profile currently verified? (yes/no)

First profile reset: yes
Second profile reset: no (as an experiment I did not connect to my custodial wallet - received the same exact errors)

What date did you connect a your Brave Rewards Profile?

12/12/23 on my first reset and 16/12/23 on my second reset

Have you been able to successfully receive payments in the past?

no payments received yet

Are you using a VPN? (yes/no)

no

Are you in a supported region (see here for list of supported regions)?

yes

[chriscat]

426 errors should be OK. We will make a change that’ll remove them, but it’s due to the browser still hitting an endpoint related to legacy vBAT points, even though vBAT has now been deprecated/sunsetted. See here:

Remove calls to `/promotions` endpoint