keybase claims my web identity broke while it's clearly working

Keybase sends me mails about my web identity being broken, while the well-known file is valid and accessible.

Running `keybase prove web` again claims there's already an ownership claim, and any attempt to overwrite it results in an error that a "live proof (...) already exists".

```
$ keybase prove web https://wouter.bolsterl.ee
You already have claimed ownership of https://wouter.bolsterl.ee; overwrite? [y/N] y
warn: You'll be asked to post a file available at
warn: https://wouter.bolsterl.ee/.well-known/keybase.txt
warn: or https://wouter.bolsterl.ee/keybase.txt
Proceed? [y/N] y
...
error: A live proof for https://wouter.bolsterl.ee already exists (error #230)
```

Is this a Keybase issue? If not, what I should I do to fix this?

The issue provides no repository file or test entry point; begin by reproducing the `keybase prove web https://wouter.bolsterl.ee` flow and checking the reported well-known URLs. Done means determining whether the live-proof error is a Keybase defect or an identity/site-state issue and documenting the concrete next step.

Written by the indexing model from the issue text.