[bug] Owncast follow doens't seem to work #1097

Closed
opened 2026-03-29 13:23:14 +00:00 by YokaiRick · 3 comments
Contributor

Your setup

OTP

Extra details

Debian13

Version

3.18.1-0-gbfc5de4--develop-

PostgreSQL version

17

What were you trying to do?

Following a new OwncastUser doesn't seem to work currently -> https://stream.revenge.day/ // @revengeday@stream.revenge.day

Either via ostatus follow (i'tll throw an internal server server error), or directly via akkoma fronted, where i can find the user, but clicking on 'follow' doesn't have any effect.

What did you expect to happen?

Following the user ;)

What actually happened?

Nothing, execpt an error in the logs

Logs

Mar 29 13:15:57 akkoma pleroma[199062]: 13:15:57.485 request_id=GKFSPrddKBRqk5sACOuS [error] Internal server error: %MatchError{term: {true, 0}}
Mar 29 13:15:57 akkoma pleroma[199062]: 13:15:57.486 [error] #PID<0.2000510.0> running Pleroma.Web.Endpoint (connection #PID<0.2000497.0>, stream id 1) terminated
Mar 29 13:15:57 akkoma pleroma[199062]: Server: a.n0id.space:80 (http)
Mar 29 13:15:57 akkoma pleroma[199062]: Request: POST /api/v1/accounts/B4kb3qE7llBGxLoysS/follow
Mar 29 13:15:57 akkoma pleroma[199062]: ** (exit) an exception was raised:
Mar 29 13:15:57 akkoma pleroma[199062]:     ** (MatchError) no match of right hand side value: {true, 0}
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user/fetcher.ex:203: Pleroma.User.Fetcher.fetch_follow_information_for_user/1
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1386: Pleroma.User.fetch_follow_information/1
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1375: Pleroma.User.maybe_fetch_follow_information/1
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1414: Pleroma.User.update_follower_count/1
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/following_relationship.ex:103: Pleroma.FollowingRelationship.after_update/3
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/web/activity_pub/side_effects.ex:110: Pleroma.Web.ActivityPub.SideEffects.handle/2
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/web/activity_pub/pipeline.ex:50: Pleroma.Web.ActivityPub.Pipeline.do_common_pipeline/2
Mar 29 13:15:57 akkoma pleroma[199062]:         (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/repo.ex:6: anonymous fn/1 in Pleroma.Repo.transaction/2

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup OTP ### Extra details Debian13 ### Version 3.18.1-0-gbfc5de4--develop- ### PostgreSQL version 17 ### What were you trying to do? Following a new OwncastUser doesn't seem to work currently -> https://stream.revenge.day/ // @revengeday@stream.revenge.day Either via ostatus follow (i'tll throw an internal server server error), or directly via akkoma fronted, where i can find the user, but clicking on 'follow' doesn't have any effect. ### What did you expect to happen? Following the user ;) ### What actually happened? Nothing, execpt an error in the logs ### Logs ```shell Mar 29 13:15:57 akkoma pleroma[199062]: 13:15:57.485 request_id=GKFSPrddKBRqk5sACOuS [error] Internal server error: %MatchError{term: {true, 0}} Mar 29 13:15:57 akkoma pleroma[199062]: 13:15:57.486 [error] #PID<0.2000510.0> running Pleroma.Web.Endpoint (connection #PID<0.2000497.0>, stream id 1) terminated Mar 29 13:15:57 akkoma pleroma[199062]: Server: a.n0id.space:80 (http) Mar 29 13:15:57 akkoma pleroma[199062]: Request: POST /api/v1/accounts/B4kb3qE7llBGxLoysS/follow Mar 29 13:15:57 akkoma pleroma[199062]: ** (exit) an exception was raised: Mar 29 13:15:57 akkoma pleroma[199062]: ** (MatchError) no match of right hand side value: {true, 0} Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user/fetcher.ex:203: Pleroma.User.Fetcher.fetch_follow_information_for_user/1 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1386: Pleroma.User.fetch_follow_information/1 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1375: Pleroma.User.maybe_fetch_follow_information/1 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/user.ex:1414: Pleroma.User.update_follower_count/1 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/following_relationship.ex:103: Pleroma.FollowingRelationship.after_update/3 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/web/activity_pub/side_effects.ex:110: Pleroma.Web.ActivityPub.SideEffects.handle/2 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/web/activity_pub/pipeline.ex:50: Pleroma.Web.ActivityPub.Pipeline.do_common_pipeline/2 Mar 29 13:15:57 akkoma pleroma[199062]: (pleroma 3.18.1-0-gbfc5de4--develop-) lib/pleroma/repo.ex:6: anonymous fn/1 in Pleroma.Repo.transaction/2 ``` ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.
Author
Contributor

I tried it with different owncast instaces, they throw the same error.
It worked in the past, so either sth changed on our or owncasts side ^^v

I tried it with different owncast instaces, they throw the same error. It worked in the past, so either sth changed on our or owncasts side ^^v
Owner

yes, i forgot to adjust a fallback clause (for actors not advertise one of the follow collections) when adding proper detection for hidden follow* counts, sorry

But the good news is, i believe that was already fixed in 792b1b8a09

yes, i forgot to adjust a fallback clause *(for actors not advertise one of the follow* collections) when adding proper detection for hidden follow\* counts, sorry But the good news is, i believe that was already fixed in 792b1b8a09cd3697589f503fd7bb9c21853ebcf3
Author
Contributor

Heck.. this is embarrassing, I'm normally the person to tell ppl on fedi they should keep their instance up2date 😓
Thanks!!!.. updated it and it works.

Heck.. this is embarrassing, I'm normally the person to tell ppl on fedi they should keep their instance up2date 😓 Thanks!!!.. updated it and it works.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AkkomaGang/akkoma#1097
No description provided.