# Unsupported address for an image when published via ActivityPub **URL:** https://meta.discourse.org/t/unsupported-address-for-an-image-when-published-via-activitypub/365923 **Category:** Support **Tags:** activitypub **Created:** [May 13, 2025, 3:10pm UTC](https://meta.discourse.org/t/unsupported-address-for-an-image-when-published-via-activitypub/365923 "2025-05-13T15:10:35Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster) #### Post date: [May 13, 2025, 3:10pm UTC](https://meta.discourse.org/t/unsupported-address-for-an-image-when-published-via-activitypub/365923/1 "2025-05-13T15:10:36Z")
We got support for images when a post is federated using ActivityPub. That was really nice. But at the same time, those images disappeared from Mastodon. When trying to open such broken images, Mastodon (or Mona-app 🤷‍♂️) says that the address of the image is unsupported. When I open it using PWA, that message/toot indicates that the preview isn’t accessible (sorry, not accurate translations, but my setups speak mostly Finnish). When I click it, the image opens and shows the URL of my S3 bucket (as it should, according to my settings in Discourse). Now I don’t know if this comes from: - Discourse - my setup, like using S3 for images - Mastodon (or my instance) - Mona/PWA - ActivityPub [Here](https://foorumi.katiska.eu/t/turun-foli-laajentaa-reitin-kasnasin/14865) is the topic in Discourse, and this might help a bit: [https://foorumi.katiska.eu/ap/object/acfff634ebeeffdf95f922193bd58ca2](https://foorumi.katiska.eu/ap/object/acfff634ebeeffdf95f922193bd58ca2) The expectation is that images are visible, even when the origin is somewhere else — using clouds and CDNs is really common, even in the Mastodon world. --- _[View the full topic](https://meta.discourse.org/t/unsupported-address-for-an-image-when-published-via-activitypub/365923)._