Recent CDN glitches in Forge Custom UI apps

Recently, Atlassian updated their CDN infrastructure so that apps no longer need to declare egress when fetching icons (e.g., issue type icons, avatars, etc.). Since then, we got the second customer reaching to use with strange error about CDN. I am not sure if that is the cause, but we haven’t received such reports before (almost a year on the marketplace).

31-01-2025

“The connection was reset.” and “1fhj3es-2o453jn0am-2j9o4b6uzs–13ujuo1-aba8mef21-1of3u04jzc.cdn.prod.atlassian-dev.net unexpectedly closed the connection.“

In the first case, the issue resolved itself after approximately 4 hours.

11-02-2025 (today)

In the second case, the customer told us that he enabled the allowlist and wonders if that’s the problem and how to add our IP (which is not ours—it’s part of Atlassian’s CDN)

Has anybody experienced similar problems lately?

1 Like

I don’t see the domain ‘cdn.prod.atlassian-dev.net’ listed among Atlassian’s domains:
IP addresses and domains for Atlassian cloud products | Atlassian Support

1 Like

One of our customers has reported recently that “*.cdn.prod.atlassian-dev.net” unexpectedly closed the connection, so our app was not usable.
The app was working fine in our Jira at the same time, but served from different host.

There is an open ticket related to this problem: https://jira.atlassian.com/browse/ECO-663