Uphold account disconnected and Error on reconnect

[cybardev]

Description

I got disconnected from Uphold (probably because of the 90 days re-authorization). When I click on the grey "Disconnected" button in the Rewards Settings...

...the last time I got disconnected, it took me to Uphold and successfully connected. Now it does take me to Uphold and I click on authorize and put my 2FA code correctly. But after that, the Uphold tab closes and in the Rewards Settings tab, it shows an error popup (screenshot below). The URL of the Rewards tab says "The user is geoblocked".

Steps to Reproduce

1. Disconnect Brave from Uphold
2. Go to brave://rewards/
3. Click the grey "Disconnected" button to attempt to reconnect Uphold wallet
4. Fill in Uphold account information and Authorize Brave
5. Return to brave://rewards/ and see an Error popup

Actual result:

This is the URL of the error: brave://rewards/uphold/authorization?error=invalid_request&error_description=The%20user%20is%20geoblocked

Expected result:

I should be able to connect my wallet without issues like I did previously.

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

Brave	1.19.92 Chromium: 88.0.4324.152 (Official Build) unknown (64-bit)
Revision	6579930fc53b4dc589c042bec9d0a3778326974d-refs/branch-heads/4324@{#2106}
OS	Linux

Version/Channel Information:

• Can you reproduce this issue with the current release? Yes
• Can you reproduce this issue with the beta channel? Unsure
• Can you reproduce this issue with the nightly channel? Unsure

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? Unsure

Miscellaneous Information:

I live in Bangladesh, if that has something to do with geoblocking, and if there's anything I can do to connect my wallet (Tor, VPN, etc.). Also, I did complete the KYC steps for Uphold when I first started using Brave (probably last year or the year before, I forgot).

[cybardev]

And the issue seems to be fixed now, though I don't know how. Thanks.