Not enough debugging information for me to fix my failing web proof

My [web proof](https://andrew.kvalhe.im/keybase.txt) is failing and it's not clear to me what I've done wrong:

``` console
$ keybase --debug id AndrewKvalheim
...
debug: +++++ refresh link
debug: ||||| Proof_id = c7c89043b2ce3e63c7c63110
debug: ||||| request proof refresh for id=c7c89043b2ce3e63c7c63110
debug: ++++++ request to sig/remote_proof (https://api.keybase.io:443/_/api/1.0/sig/remote_proof.json?proof_id=c7c89043b2ce3e63c7c63110)
debug: |||||| Adding a custom CA for host api.keybase.io when tls=true
debug: ------ request to sig/remote_proof -> null
debug: ----- refresh_link
debug: |||| remote service desc is {"hostname":"andrew.kvalhe.im","protocol":"https:"}
✖ admin of andrew.kvalhe.im via HTTPS: (failed with code 201)
debug: ---- andrewkvalheim: checked remote generic_web_site proof
...
```

I didn't see any network traffic to my site while running this. The mentioned API call returns `"api_url": null` so I think I'm hitting [this condition](https://github.com/keybase/node-client/blob/3ab3f4494f2fb5a39f30b38b64dece3bc714b7b9/src/sigchain.iced#L207), but I don't know where to go from there.

Reproduce the failure with `keybase --debug id AndrewKvalheim`, then inspect the `sig/remote_proof` API response and the condition around line 207 of `src/sigchain.iced`. Trace why `api_url` is null and determine what diagnostic output or handling is needed so a failing web proof can be investigated without guessing.

Written by the indexing model from the issue text.