My instance can't get any media from one specific domain

My instance is brand new (a few days old).

The other day I saw that I had a missing avatar from someone mentioned in my feed.

I did some digging, and it seems my instance can’t fetch any media from that instance.

Text within posts works, and the text in the users profiles work, but no profile images, and no media in their posts.

If I enter the url to any user from that domain, in the search box on my instance, I get errors in both error.log som nginx, and also from journalctl for the akkoma service.

Example of one user I tried with: Pixel Light (@pixellight@pony.social) - Ponies on Mastodon

Here is a snippet from ningx error.log and journalctl for akkoma service, at the time I do the search.

----- journalctl for akkoma -----
Feb 14 13:47:12 akkoma pleroma[236]: 13:47:12.093 request_id=GCQXK4vjWtUKE20AAxcD [error] Could not figure out who owns the key https://witter.cz/users/taya365philippines#main-key
Feb 14 13:47:12 akkoma pleroma[236]: 13:47:12.094 request_id=GCQXK4vjWtUKE20AAxcD [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:12 akkoma pleroma[236]: 13:47:12.140 request_id=GCQXK4vjWtUKE20AAxcD [error] Could not figure out who owns the key https://witter.cz/users/taya365philippines#main-key
Feb 14 13:47:12 akkoma pleroma[236]: 13:47:12.140 request_id=GCQXK4vjWtUKE20AAxcD [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:17 akkoma pleroma[236]: 13:47:17.692 request_id=GCQXLNSNImK48e8AAxeD [error] Could not figure out who owns the key https://aethy.com/users/RoyalFlush#main-key
Feb 14 13:47:17 akkoma pleroma[236]: 13:47:17.692 request_id=GCQXLNSNImK48e8AAxeD [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:17 akkoma pleroma[236]: 13:47:17.767 request_id=GCQXLNSNImK48e8AAxeD [error] Could not figure out who owns the key https://aethy.com/users/RoyalFlush#main-key
Feb 14 13:47:17 akkoma pleroma[236]: 13:47:17.767 request_id=GCQXLNSNImK48e8AAxeD [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:34 akkoma pleroma[236]: 13:47:34.688 [error] Object rejected while fetching https://pony.social/@pixellight {:transmogrifier, :error}
Feb 14 13:47:36 akkoma pleroma[236]: 13:47:36.520 request_id=GCQXMUTZTJwbDMQACCEB [error] Could not figure out who owns the key https://mastodon.social/users/graphicpro#main-key
Feb 14 13:47:36 akkoma pleroma[236]: 13:47:36.520 request_id=GCQXMUTZTJwbDMQACCEB [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:36 akkoma pleroma[236]: 13:47:36.533 request_id=GCQXMUTZTJwbDMQACCEB [error] Could not figure out who owns the key https://mastodon.social/users/graphicpro#main-key
Feb 14 13:47:36 akkoma pleroma[236]: 13:47:36.533 request_id=GCQXMUTZTJwbDMQACCEB [error] Failed to extract actor_id from signature: {:error, :key_owner_not_found}
Feb 14 13:47:36 akkoma pleroma[236]: 13:47:36.987 [info] Rich media backfill: streaming update for activity Ar6wTJh3R93o7fBnWa



----- Nginx error.log -----
2025/02/14 13:47:35 [error] 230#230: *15587 unexpected range in slice response: 0-1048576 while reading response header from upstream, client: 192.168.0.5, server: media.fedi.arutaz.net, request: "GET /proxy/gJa6DXtIC_HhkkrjY4IZun-260o/aHR0cHM6Ly9jZG4ucG9ueS5zb2NpYWwvYWNjb3VudHMvYXZhdGFycy8xMDkvMjUyLzg0OS80NTMvMTk1LzczMC9vcmlnaW5hbC8xN2ZjOWJlMGU4MDI0ZWZjLmdpZg/17fc9be0e8024efc.gif HTTP/1.1", upstream: "http://127.0.0.1:4000/proxy/gJa6DXtIC_HhkkrjY4IZun-260o/aHR0cHM6Ly9jZG4ucG9ueS5zb2NpYWwvYWNjb3VudHMvYXZhdGFycy8xMDkvMjUyLzg0OS80NTMvMTk1LzczMC9vcmlnaW5hbC8xN2ZjOWJlMGU4MDI0ZWZjLmdpZg/17fc9be0e8024efc.gif", host: "media.fedi.arutaz.net"

I created an account on another Akkoma instance now, and that instance can’t either get any media from the pony.social instance.

However I have tried with two different Mastodon instances, and both of them can load media just fine from pony.social.

So at this point I’m not sure if there is a problem with Akkoma or with that instance.
(They are running Mastodon v4.4.0-nightly.2024-12-21+glitch).

It was not only my domain. that had problems.
And it works now, so most likely an issue with that domain (now fixed).

1 Like