# Problemen met gekoppelde actoren
**URL:** https://meta.discourse.org/t/issues-with-linked-actors/343469
**Category:** Bug
**Tags:** activitypub, fixed
**Created:** [19 december 2024 om 20:55 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469 "2024-12-19T20:55:15Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [19 december 2024 om 20:55 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/1 "2024-12-19T20:55:15Z")
We just merged [a commit](https://github.com/discourse/discourse-activity-pub/commit/6fc7971d3e0af57e1e9bf88de9c177de13e20e17) that adds support for Discourse-to-Discourse linked actors on the ActivityPub plugin, however, on testing in two different instances, I am seeing issues. Filing them all here @angus so that they’re grouped together.
**Discourse-to-Discourse verification** : in a personal Discourse instance, I can’t add a Discourse Linked Actor from `meta.discourse.org`, initially I got a “failed to verify” client error, and then a timeout.
Screenshots:
Same error when trying to link my personal instance account from meta.
**Discourse-to-Mastodon verification** : on the personal instance, this worked Ok! Here on meta though, I can’t seem to get past the verify step for `mastodon.social`, I get this error: `An error occurred: The access token is invalid Failed to verify client`.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [20 december 2024 om 14:17 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/2 "2024-12-20T14:17:13Z")
Just a note that I’ve started working on this and will have an update / PR soon.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [20 december 2024 om 18:49 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/3 "2024-12-20T18:49:44Z")
@pmusaraj Just as an initial measure I’ve made a PR that adds settings for the rate limiting of user api key clients (which will make this hard to test this).
[https://github.com/discourse/discourse/pull/30402](https://github.com/discourse/discourse/pull/30402)
Could you also just check that `discourse-activity-pub:read` scope is added to the `allow user_api key client scopes` site setting. It should be automatically, but worth checking.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [3 januari 2025 om 17:09 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/4 "2025-01-03T17:09:13Z")
@pmusaraj Just a note that in my testing on a production instance this PR
[https://github.com/discourse/discourse/pull/30544](https://github.com/discourse/discourse/pull/30544)
fixed this issue:
> [@pmusaraj](#):
>
> Discourse-to-Discourse verification
If you could let me know when this is live on meta, we can test here too.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [4 januari 2025 om 04:18 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/5 "2025-01-04T04:18:30Z")
This change is now live on meta. With my own self-hosted instance (also up-to-date with this change), I am getting a step further, but got this error after authorizing:
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [4 januari 2025 om 13:47 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/6 "2025-01-04T13:47:34Z")
I think this means we’ve fixed this issue. This error will currently occur if you don’t already have an actor on the instance as user actors are created on demand (i.e. it’s expected, albeit the message could be improved). I think this is one case where we should create them if they don’t exist. This will do that:
[https://github.com/discourse/discourse-activity-pub/pull/147](https://github.com/discourse/discourse-activity-pub/pull/147)
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [6 januari 2025 om 16:46 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/7 "2025-01-06T16:46:09Z")
👍 that last PR fixes Discourse-to-Discourse authorization on my self-hosted instance, thanks!
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [7 januari 2025 om 13:18 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/8 "2025-01-07T13:18:56Z")
> [@pmusaraj](#):
>
> **Discourse-to-Mastodon verification** : on the personal instance, this worked Ok! Here on meta though, I can’t seem to get past the verify step for `mastodon.social`, I get this error: `An error occurred: The access token is invalid Failed to verify client`.
I think this may be indicative of an old/destroyed OAuth app on the Mastodon side of things. Just a note that in my own tests with mastodon.social (on production instances), I was able to verify without issue. I’ve raised a PR to address this potential cause of the issue:
[https://github.com/discourse/discourse-activity-pub/pull/151](https://github.com/discourse/discourse-activity-pub/pull/151)
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [7 januari 2025 om 13:44 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/9 "2025-01-07T13:44:50Z")
Or is used the Hub.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [7 januari 2025 om 16:11 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/10 "2025-01-07T16:11:57Z")
@pmusaraj Thanks for the merge. Just a note that I was just able to successfully authorize my Mastodon account on `mastodon.social` here on meta, so it looks like that PR has fixed it, but let me know if you have any more issues.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [7 januari 2025 om 16:12 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/11 "2025-01-07T16:12:50Z")
Yes, indeed, it worked for me as well. Awesome, thank you!
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [8 januari 2025 om 13:00 UTC](https://meta.discourse.org/t/issues-with-linked-actors/343469/12 "2025-01-08T13:00:28Z")
This topic was automatically closed after 20 hours. New replies are no longer allowed.