Unable to fetch attachments

[wimg]

Self-Hosted Version

25.9.0

CPU Architecture

x86_64

Docker Version

28.5.0

Docker Compose Version

28.5.0

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

1. Upgrade from Sentry 25.1.0 to 25.8.0
2. Go to an entry from before the upgrade
3. Notice "An error occurred while fetching attachments" and "There was an error loading data"

Expected Result

All blocks loading correctly

Actual Result

Event ID

No response

[wimg]

I noticed in the meantime that I was supposed to upgrade to 25.5.1 first. But without reading the upgrade instructions every single time, people miss that. So doesn't it make sense to put a check in the install.sh script, so it verifies that you are indeed not skipping one of the releases that you must pass by ?

Also, not sure how to proceed now, since I suppose downgrading won't work. Any suggestions ?

[myonlylonely]

I have the exactly the same issue. Upgrading to 25.8 is fine, but after upgrading to 25.9, this issue occurs.
And BTW I have tried, downgrade do work, I have just tried.
@wimg You could downgrade to 25.8 for now.
Upgrading to 25.9 still does not working for me.

[Chasx]

We're experiencing the same.

Reverted my VM to the 25.8 snapshot I made before upgrading and everything works as expected but upgrading by downloading the release from https://github.com/getsentry/self-hosted/releases/tag/25.9.0 and running ./install.sh results in the same issue as mentioned above.

[wimg]

Hmm that makes it seem as if it's 25.9.0 issue, not the fact that I skipped 25.5.1 ?

[Chasx]

I’m not entirely sure, but I don’t think so. We’ve had several issues with older versions in the past because I hadn’t upgraded through all the ‘hard stops’ as documented in the Sentry upgrade guide: https://develop.sentry.dev/self-hosted/releases/#hard-stops. Earlier this year, I manually upgraded passing the versions listed in that document, and since then, upgrades have gone smoothly.

Before version 25.8, I believe we also ran other versions like 25.7 and 25.6, as I have snapshots from the months those versions were released. We usually create those snapshots when upgrading to a newer version.

[myonlylonely]

I upgraded from 25.7 to 25.9, and before this, I do follow the instructions to have the hard stop at 25.5 to 25.5.1. So I think this issue is only related to 25.9.

[cyfran]

I have some issue on 25.9 with "error occurred while fetching attachments".
I thing correctly its associated with sentry-self-hosted-relay-1 I see in docker logs errors like

2025-10-08T13:46:40.636146Z ERROR relay_server::services::projects::source::upstream: error fetching project state 8b7620f43375fd8f779d094df8bb21af: deadline exceeded errors=0 pending=268 tags.did_error=false tags.was_pending=true tags.project_key="8b7620f43375fd8f779d094df8bb21af"
2025-10-08T13:46:40.636206Z ERROR relay_server::services::projects::cache::service: failed to fetch project from source: Fetch { project_key: ProjectKey("8b7620f43375fd8f779d094df8bb21af"), previous_fetch: None, initiated: Instant { tv_sec: 7284, tv_nsec: 747176400 }, when: Some(Instant { tv_sec: 8446, tv_nsec: 863228191 }), revision: Revision(None) } tags.project_key="8b7620f43375fd8f779d094df8bb21af" tags.has_revision=false error=upstream error failed to send message to service error.sources=[failed to send message to service]

How we can resolve this? Can I revert/downgrade to 25.8 by install.sh script?

[myonlylonely]

@cyfran No official response yet. But I did try to downgrade to 25.8 successfully using install.sh script. Just change the docker image tag in .env to 25.8.

[myonlylonely]

@cyfran BTW, did you change SENTRY_BIND in .env fromSENTRY_BIND=9000 to something like SENTRY_BIND=127.0.0.1:9000?

[cyfran]

No:

[root@log self-hosted]# cat .env
COMPOSE_PROJECT_NAME=sentry-self-hosted
# Set COMPOSE_PROFILES to "feature-complete" to enable all features
# To enable errors monitoring only, set COMPOSE_PROFILES=errors-only
# See https://develop.sentry.dev/self-hosted/experimental/errors-only/
COMPOSE_PROFILES=feature-complete
SENTRY_EVENT_RETENTION_DAYS=90
# You can either use a port number or an IP:PORT combo for SENTRY_BIND
# See https://docs.docker.com/compose/compose-file/#ports for more
SENTRY_BIND=9000
# Set SENTRY_MAIL_HOST to a valid FQDN (host/domain name) to be able to send emails!
# SENTRY_MAIL_HOST=example.com
SENTRY_IMAGE=ghcr.io/getsentry/sentry:25.9.0
SNUBA_IMAGE=ghcr.io/getsentry/snuba:25.9.0
RELAY_IMAGE=ghcr.io/getsentry/relay:25.9.0
SYMBOLICATOR_IMAGE=ghcr.io/getsentry/symbolicator:25.9.0
TASKBROKER_IMAGE=ghcr.io/getsentry/taskbroker:25.9.0
VROOM_IMAGE=ghcr.io/getsentry/vroom:25.9.0
UPTIME_CHECKER_IMAGE=ghcr.io/getsentry/uptime-checker:25.9.0
HEALTHCHECK_INTERVAL=30s
HEALTHCHECK_TIMEOUT=1m30s
HEALTHCHECK_RETRIES=10
HEALTHCHECK_START_PERIOD=10s
HEALTHCHECK_FILE_INTERVAL=60s
HEALTHCHECK_FILE_TIMEOUT=10s
HEALTHCHECK_FILE_RETRIES=3
HEALTHCHECK_FILE_START_PERIOD=600s
# Set SETUP_JS_SDK_ASSETS to 1 to enable the setup of JS SDK assets
# SETUP_JS_SDK_ASSETS=1
[root@log self-hosted]#