AkkomaGang/akkoma

Fork 99

[bug] unable to follow some activitypub relays #876

New issue

Closed

opened 2025-03-03 06:46:55 +00:00 by grassblock · 1 comment

grassblock commented

2025-03-03 06:46:55 +00:00

Your setup

Docker

Extra details

Debian 12 with podman in distro package

Version

3.15.1

PostgreSQL version

What were you trying to do?

As mentioned in #858 (comment) and #858 (comment) , I was trying to follow relays like https://relay.nya.one & https://relay.pari.cafe & https://relay.toot.yukimochi.jp .

What did you expect to happen?

at least I should subscribe these mentioned relays successfully

What actually happened?

The addition and deletion of these relays ware successful in 3.15.1 but they can't follow back.

Logs

01:27:34.732 request_id=GCkmrLQA0vDU4_UAAjGD [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known

01:27:34.802 request_id=GCkmrKs5MYB3uX8AAjFj [error] Object rejected while fetching https://relay.pari.cafe/actor {:strict_id, {:error, "https://relay.pari.cafe/actor#main-key"}}

01:27:34.803 request_id=GCkmrKs5MYB3uX8AAjFj [error] Failed to acquire key from signature: https://relay.pari.cafe/actor {:error, "Could not fetch key"}

01:27:55.938 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "https://relay.nya.one/actor#main-key"}}

01:27:55.983 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "https://relay.nya.one/actor#main-key"}}

01:27:55.984 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to acquire key from signature: https://relay.nya.one/actor {:error, "Could not fetch key"}

01:27:55.985 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known

01:27:56.035 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "htt
ps://relay.nya.one/actor#main-key"}}

01:27:56.035 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to acquire key from signature: https://relay.nya.one/actor {:error, "Could not fetch key"}

01:27:56.037 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known

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 Docker ### Extra details Debian 12 with podman in distro package ### Version 3.15.1 ### PostgreSQL version 14 ### What were you trying to do? As mentioned in https://akkoma.dev/AkkomaGang/akkoma/issues/858#issuecomment-13749 and https://akkoma.dev/AkkomaGang/akkoma/issues/858#issuecomment-13727 , I was trying to follow relays like https://relay.nya.one & https://relay.pari.cafe & https://relay.toot.yukimochi.jp . ### What did you expect to happen? at least I should subscribe these mentioned relays successfully ### What actually happened? The addition and deletion of these relays ware successful in 3.15.1 but they can't follow back. ![image](/attachments/25a599f0-4599-4e48-a0ec-304f7ea81b70) ### Logs ```shell 01:27:34.732 request_id=GCkmrLQA0vDU4_UAAjGD [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known 01:27:34.802 request_id=GCkmrKs5MYB3uX8AAjFj [error] Object rejected while fetching https://relay.pari.cafe/actor {:strict_id, {:error, "https://relay.pari.cafe/actor#main-key"}} 01:27:34.803 request_id=GCkmrKs5MYB3uX8AAjFj [error] Failed to acquire key from signature: https://relay.pari.cafe/actor {:error, "Could not fetch key"} 01:27:55.938 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "https://relay.nya.one/actor#main-key"}} 01:27:55.983 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "https://relay.nya.one/actor#main-key"}} 01:27:55.984 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to acquire key from signature: https://relay.nya.one/actor {:error, "Could not fetch key"} 01:27:55.985 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known 01:27:56.035 request_id=GCkmsa0wTNBJkegAAbfl [error] Object rejected while fetching https://relay.nya.one/actor {:strict_id, {:error, "htt ps://relay.nya.one/actor#main-key"}} 01:27:56.035 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to acquire key from signature: https://relay.nya.one/actor {:error, "Could not fetch key"} 01:27:56.037 request_id=GCkmsa0wTNBJkegAAbfl [error] Failed to extract actor_id from signature: signing key https://relay.nya.one/actor not known ``` ### 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.

image.png

119 KiB

grassblock added the

bug

label 2025-03-03 06:46:55 +00:00

grassblock commented

2025-03-03 06:57:11 +00:00

Author

I also tried follow https://relay.isle.moe. the issues are the same. Their logs:

INFO[283234] RelayState reloaded                          
INFO[283234] Accepted Follow Request : https://portal.gb0.dev/relay 
INFO[283234] Sent MutuallyFollow Request : https://portal.gb0.dev/relay

DEBU[283258] https://portal.gb0.dev/relay/inbox 400       
ERROR: 2025/03/03 06:49:40 worker.go:370 Failed processing task task_0c6f6111-f9ff-4b25-8f59-86fdba1549ba. Error = https://portal.gb0.dev/relay/inbox: 400 Bad Request

I also tried follow https://relay.isle.moe. the issues are the same. Their logs: ``` INFO[283234] RelayState reloaded INFO[283234] Accepted Follow Request : https://portal.gb0.dev/relay INFO[283234] Sent MutuallyFollow Request : https://portal.gb0.dev/relay ``` ``` DEBU[283258] https://portal.gb0.dev/relay/inbox 400 ERROR: 2025/03/03 06:49:40 worker.go:370 Failed processing task task_0c6f6111-f9ff-4b25-8f59-86fdba1549ba. Error = https://portal.gb0.dev/relay/inbox: 400 Bad Request ```

grassblock closed this issue

2025-03-03 13:10:40 +00:00

No milestone

No project

No assignees

1 participant

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#876

No description provided.

Rows
Columns