-
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 Loading...