How to debug connectivity issues with ActivityPub

Unfortuntately I’m seeing the same issues in the logs on the Discourse side of this, and you’re not showing up as a follower.

As you can see I just successfully followed from two other mastodon servers. I signed up for an account on mastodon.ie (“irishangus”) and I’m also seeing the same issue you’re seeing, i.e.

[Discourse Activity Pub] Failed to process https://mastodon.ie/users/irishangus: Could not resolve actor

Moreover, this actor issue log is strange, normally mastodon actor uris don’t look like this:

[Discourse Activity Pub] Failed to process https://mastodon.ie/aec0cbc8-c3bd-4eb2-a4f4-f491f8331841: Could not create actor

This all suggests to me that the issue is indeed specific to mastodon.ie. I’ll investigate further tomorrow.

2 Likes

I have been informed by the mastodon.ie admins that Authorized Fetch is enabled on the server and that is probably what is causing this to fail:

1 Like

Thanks for this note. The plugin does support Mastodon’s implementation of HTTP signatures, which is what Authorized Fetch is based on, however there may be some quirks with that server, or the implemetation more broadly. This kind of issue typically takes some time to debug properly, so I’ve put aside some time later this week to attempt that.

2 Likes