-
Bug
-
Resolution: Fixed
-
High
-
Severity 2 - Major
Issue Summary
Forge app users receive an error message when accessing a Forge app.
The webpage at https://[dynamic hostname].cdn.prod.atlassian-dev.net/[context path] might be temporarily down or it may have moved permanently to a new web address.
Or a message such as
https://[dynamic hostname].cdn.prod.atlassian-dev.net/'s server IP address could not be found.
This only occurs on some corporate VPNs or certain DNS systems such as OpenDNS.
This is similar to
but more generic, as that case was about jira:issueViewBackgroundScript
Steps to Reproduce
- Install a Forge app with a globalPage or similar component that requires an iframe into a site
- Configure the DNS to reject requests to Dynamic DNS hostnames or purge the cache quickly for hostnames that have a short TTL.
- Access the globalPage
Expected Results
The Forge app displays correctly.
Actual Results
The iframe with the Forge app shows
Workaround
Ensure the DNS resolves the hostname to the CloudFlare DNS sites. You can test this with dig and testing the domain name in the error message, replace the hostname here as necessary
$ dig [dynamic hostname].cdn.prod.atlassian-dev.net ; <<>> DiG 9.10.6 <<>> [dynamic hostname].cdn.prod.atlassian-dev.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10807 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1220 ;; QUESTION SECTION: ;[dynamic hostname].prod.atlassian-dev.net. IN A ;; ANSWER SECTION: [dynamic hostname].cdn.prod.atlassian-dev.net. 60 IN CNAME d1qem4azactru2.cloudfront.net. d1qem4azactru2.cloudfront.net. 60 IN A 18.67.93.9 d1qem4azactru2.cloudfront.net. 60 IN A 18.67.93.107 d1qem4azactru2.cloudfront.net. 60 IN A 18.67.93.17 d1qem4azactru2.cloudfront.net. 60 IN A 18.67.93.40 ;; Query time: 27 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Fri Feb 14 10:55:03 AEDT 2025 ;; MSG SIZE rcvd: 221
Note here, the IP addresses will be different based on your location, but the should all resolve to a cloudfront.net site.
You can also add the CloudFront (and other AWS) IP addresses as necessary as documented in
- is caused by
-
EXT-2807 Failed to load
[ECO-663] When using a Forge app on certain networks the app shows a error page that says it might be temporarily down or it may have moved permanently to a new web address.
Hi all,
Please follow https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/.
To ensure seamless access to Forge apps installed, firewalls or security rules need to be configured to allow traffic from hostnames that follow the pattern https://<app-identification>.cdn.prod.atlassian-dev.net. Note that the <app-identification> is dynamic and will vary for different installations of the applications. This configuration is essential for the proper functioning of our app within your network environment.
If you face further issues, these are the specific IPs you will need to enable in your firewall config:
104.192.136.0/21 185.166.140.0/22 13.35.248.0/24 13.227.180.0/24 13.227.213.0/24
Let us know if you continue to experience these issues.
Cheers,
Yuwei
All comments
Hi all,
Please follow https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/.
To ensure seamless access to Forge apps installed, firewalls or security rules need to be configured to allow traffic from hostnames that follow the pattern https://<app-identification>.cdn.prod.atlassian-dev.net. Note that the <app-identification> is dynamic and will vary for different installations of the applications. This configuration is essential for the proper functioning of our app within your network environment.
If you face further issues, these are the specific IPs you will need to enable in your firewall config:
104.192.136.0/21 185.166.140.0/22 13.35.248.0/24 13.227.180.0/24 13.227.213.0/24
Let us know if you continue to experience these issues.
Cheers,
Yuwei
One of our customers has reported recently that *.cdn.prod.atlassian-dev.net host 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.
We have 2 tickets opened by customers with this problem.
We need an urgent resolution.
Changing Priority to High:
- 7 tickets opened by customers and partners, highlighting the impact.
- When a ticket is opened because the customer can't using the app, partners are opening Priority-1 - Critical, as their app is not usable.
Marking this as fixed as users can follow the guidance in the pinned comment to solve these issues.