Decode / Fetch errors

I recently installed Akkoma from src on debian 12, and I’ve been able to work around most of the issues I’ve run across; however, I am getting some akkoma server connection drops and the logs show a repeat of the following type of error

pleroma: request_id=F5yHff6Fd9l-5P0ACP1y [error] Could not decode featured collection at fetch https://mastodon.world/users/luk88in/collections/featured, {:error, {:ok, %Tesla.Env{method: :get, url: "https://mastodon.world/users/luk88in/collections/featured", query: [], headers: [{"date", "Thu, 30 Nov 2023 22:35:34 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"transfer-encoding", "chunked"}, {"connection", "keep-alive"}, {"vary", "Accept-Encoding"}, {"server", "Mastodon"}, {"x-frame-options", "DENY"}, {"x-content-type-options", "nosniff"}, {"x-xss-protection", "0"}, {"referrer-policy", "same-origin"}, {"vary", "Authorization"}, {"cache-control", "max-age=180, public"}, {"content-security-policy", "default-src 'none'; frame-ancestors 'none'; form-action 'none'"}, {"x-request-id", "f8aa6a1b-37b7-4da5-ba76-97b4ce70c71c"}, {"x-runtime", "0.021997"}, {"strict-transport-security", "max-age=63072000; includeSubDomains"}, {"strict-transport-security", "max-age=31536000"}], body: "{\"error\":\"Forbidden\"}", status: 403, opts: [adapter: [receive_timeout: 15000, pool_timeout: 5000, name: MyFinch]], __module__: Tesla, __client__: %Tesla.Client{fun: nil, pre: [{Tesla.Middleware.FollowRedirects, :call, [[]]}, {Tesla.Middleware.Telemetry, :call, [[]]}], post: [], adapter: nil}}}}

 pleroma: request_id=F5yHfxmA1KuAXPwACP2C [error] Could not fetch user https://apotheke.social/users/Paolosoruco, {nil, {:error, {"Object has been deleted", "https://apotheke.social/users/Paolosoruco", 410}}}

My searches have turned up almost nothing - except a documented bug related to pleroma http header handling - which was patched months ago.

If anyone has any thoughts, I’d appreciate it.
THanks

In both cases I get a 410 for the accounts, so they don’t seem to exist any more. So i don’t think anything is really “wrong” there. Although, it would probably be better if Akkoma didn’t throw an error for that.

I noticed that the accounts didn’t exit as well - but Akkoma is logging it with Error level - it should probably log with Notify if it’s expected behavior. Thanks - still trying to understand the little beast that is Akkoma

2 Likes