403 Response in WordPress - Expected Different Site?

[willtm]

Hello, after using Aperture to read in Alltogether, Monocle, and Indigenous for several weeks, I seem to have lost the ability to do so in Alltogether and Monocle. Indigenous still seems to work.

I've looked at some similar issues to try to work through the troubleshooting steps. And that's led me to two questions:

1. Where should I place the HTML necessary to establish the Aperture pingback?

<link rel="microsub" href="https://aperture.p3k.io/microsub/389">

I know this should be elementary and may be a question for WordPress indieweb folks but I thought I would ask. And I suspect this might clear everything else up.

2. Related to that, I get the following error in Monocle. What stands out to me is the expected and from token statements. Is Aperture encountering something unexpected when attempting to use the Indieauth endpoint on my site?

{
    "code": 403,
    "header": "HTTP/1.1 403 Forbidden\r\nServer: nginx/1.14.0\r\nContent-Type: application/json\r\nTransfer-Encoding: chunked\r\nConnection: keep-alive\r\nX-Powered-By: PHP/7.2.7-1+ubuntu16.04.1+deb.sury.org+1\r\nCache-Control: no-cache, private\r\nDate: Fri, 11 Oct 2019 11:19:55 GMT",
    "body": {
        "error": "invalid_user",
        "error_description": "This token was issued to a different user",
        "debug": {
            "expected": "https://willtmonroe.com/",
            "from_token": "https://willtmonroe.com/author/admin/"
        }
    },
    "error": "",
    "error_description": "",
    "url": "https://aperture.p3k.io/microsub/390?action=channels",
    "debug": "HTTP/1.1 403 Forbidden\r\nServer: nginx/1.14.0\r\nContent-Type: application/json\r\nTransfer-Encoding: chunked\r\nConnection: keep-alive\r\nX-Powered-By: PHP/7.2.7-1+ubuntu16.04.1+deb.sury.org+1\r\nCache-Control: no-cache, private\r\nDate: Fri, 11 Oct 2019 11:19:55 GMT\r\n\r\n{\"error\":\"invalid_user\",\"error_description\":\"This token was issued to a different user\",\"debug\":{\"expected\":\"https:\\/\\/willtmonroe.com\\/\",\"from_token\":\"https:\\/\\/willtmonroe.com\\/author\\/admin\\/\"}}",
    "headers": {
        "Server": "nginx/1.14.0",
        "Content-Type": "application/json",
        "Transfer-Encoding": "chunked",
        "Connection": "keep-alive",
        "X-Powered-By": "PHP/7.2.7-1+ubuntu16.04.1+deb.sury.org+1",
        "Cache-Control": "no-cache, private",
        "Date": "Fri, 11 Oct 2019 11:19:55 GMT"
    },
    "rels": []
}

I appreciate your help. I really enjoy using my own website to read feeds but I'm still quite unsure about how to troubleshoot these technologies.

Will

[willtm]

Closing this issue. The problem was a misconfigured IndieAuth plugin setting. I needed to set the WP IndieAuth settings > Web Sign-in > Set User to Represent Site URL to my actual username instead of the "None" option that was there by default.