Misskey: Misskey is requesting the followers collection from the configured AP relay

Created on 6 Dec 2020  ·  4Comments  ·  Source: syuilo/misskey

💡 Summary

I'm running an AP relay (https://git.pleroma.social/pleroma/relay). I have configured that relay in my instance/relay settings.

My Misskey instance is constantly requesting the followers collection of the relay. But the relay doesn't have one. So, the requests are answered with a 404. But Misskey continues to request the /followers endpoint with a pretty high frequency.

I can see the same behavior with other Misskey instances in the log of the AP relay. So, it isn't specific to my instance.

Here is an excerpt from the AP relay access log. You can see approx. 30 seconds with a lot of those requests from Misskey.

xx.xxx.xxx.xx - - [06/Dec/2020:21:18:01 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:05 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:08 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:09 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:10 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:10 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:10 +0000] "GET /followers HTTP/1.1" 404 897 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:10 +0000] "GET /followers HTTP/1.1" 404 897 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:11 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:17 +0000] "GET /followers HTTP/1.1" 404 897 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:17 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:18 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:20 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 897 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 919 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:21 +0000] "GET /followers HTTP/1.1" 404 919 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:22 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:23 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:23 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:23 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:24 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:25 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:26 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:27 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:28 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:29 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:29 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:32 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:32 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:32 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:32 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:33 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:34 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:34 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:34 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:34 +0000] "GET /followers HTTP/1.1" 404 370 "-" "Misskey/12.62.2 (https://misskey.de)"
xx.xxx.xxx.xx - - [06/Dec/2020:21:18:34 +0000] "GET /followers HTTP/1.1" 404 348 "-" "Misskey/12.62.2 (https://misskey.de)"

🙂 Expected Behavior

Don't treat the configured AP relay like a general contact/follower. Don't request the /followers endpoint of an AP relay with such a high frequency.

☹️ Actual Behavior

Looks like Misskey is treating the configured AP relay like every other user/contact/follower. It is even listed in the list of local users. Do not constantly request a non-existing endpoint (/followers) from AP relays.

📌 Environment

Misskey v12.62.2
Node.js v14.15.1
PostgreSQL v12.5 (Ubuntu 12.5-0ubuntu0.20.04.1)
Redis v5.0.7
AP relay: latest version from https://git.pleroma.social/pleroma/relay running on https://relay.libranet.de/

⚠️bug?

All 4 comments

Oh! Could be I added the relay with wrong URL. I used /actor but it probably should be /inbox. I need to check that.

I have now configured the AP relay with the .../inbox path. It works.

Is there a way to get rid of that wrong local user account @relay.actor? Or as a general question: how can I completely delete a user account from the instance? I'm the admin but I cannot find a delete button or something.

Is there a way to get rid of that wrong local user account @relay.actor?

@relay.actor is the system user used for the relay feature. Therefore, it cannot be deleted.

@relay.actor is the system user used for the relay feature. Therefore, it cannot be deleted.

Hmm. Okay. Thank you. But it is confusing that the account is displayed like a normal, registered user on .../instance/users. It is even counted as local user in the instance stats.

Update concerning the original issue: The frequency of the .../followers requests went down to approx. 3 per minute. That's better. Although I don't know why. :-)

Was this page helpful?
0 / 5 - 0 ratings