We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      Issue Summary

      The Jira Server mobile app cannot connect to Jira when the bug JRASERVER-71175 is mitigated.

      JRASERVER-71175 is mitigated by either being on a version of Jira where the bug is fixed ('Fix Version/s") or by implementing the workaround dark feature, jira.redirect.anonymous.404.errors.enabled

      Steps to Reproduce

      1. Install Jira 8.9.1
      2. Configure the correct base URL
      3. Attempt to connect the Jira mobile app to it.

      Expected Results

      The app connects uneventfully.

      Testing the server-info endpoint via curl reveals:

      ➜ curl --head http://localhost:8854/j854/server-info
      HTTP/1.1 404 
      X-AREQUESTID: 680x587x1
      X-ANODEID: node1
      X-XSS-Protection: 1; mode=block
      X-Content-Type-Options: nosniff
      X-Frame-Options: SAMEORIGIN
      Content-Security-Policy: frame-ancestors 'self'
      mobile-plugin-enabled: true
      push-notification-enabled: true
      instance-name: Jira
      jira-base-url: http://localhost:8854/j854
      is-data-center: true
      X-ASEN: SEN-500
      Set-Cookie: atlassian.xsrf.token=BJLD-I2E2-XZYV-WCHE_4aad390c48c897ed4dc1f0e40ac71645357519ab_lout; Path=/j854
      X-AUSERNAME: anonymous
      Set-Cookie: JSESSIONID=828ADE16F7C117ADFD54DAB9DCCD37EF; Path=/j854; HttpOnly
      Content-Type: text/html;charset=UTF-8
      Transfer-Encoding: chunked
      Date: Tue, 30 Jun 2020 01:20:18 GMT
      

      Actual Results

      A message indicating "Can't connect to your site" is shown on Android and "Can't check compatibility" on iOS

      Testing the server-info endpoint via curl reveals:
      Example 1: Jira 8.5.4, with dark feature jira.redirect.anonymous.404.errors.enabled

      ➜ curl --head http://localhost:8854/j854/server-info
      curl: (7) Failed to connect to localhost port 8854: Connection refused

      Example 2: Jira 8.9.1

      ➜ curl --head http://localhost:8080/server-info
      HTTP/1.1 503
      X-AREQUESTID: 405x9x1
      X-XSS-Protection: 1; mode=block
      X-Content-Type-Options: nosniff
      X-Frame-Options: SAMEORIGIN
      Content-Security-Policy: frame-ancestors 'self'
      mobile-plugin-enabled: true
      push-notification-enabled: true
      instance-name: Jira
      jira-base-url: http://localhost:8080
      is-data-center: false
      new-create-metadata-api: true
      X-ASEN: SEN-500
      Retry-After: 30
      Content-Type: text/html;charset=UTF-8
      Transfer-Encoding: chunked
      Date: Tue, 30 Jun 2020 06:45:22 GMT
      Connection: close 

      Workaround

      The issue is related to a security fix and as a temporary solution this can be disabled by

      1. adding the dark feature flag jira.redirect.anonymous.404.errors.disabled, and,
      2. removing, if present, the dark feature flag jira.redirect.anonymous.404.errors.enabled

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                Issue Summary

                The Jira Server mobile app cannot connect to Jira when the bug JRASERVER-71175 is mitigated.

                JRASERVER-71175 is mitigated by either being on a version of Jira where the bug is fixed ('Fix Version/s") or by implementing the workaround dark feature, jira.redirect.anonymous.404.errors.enabled

                Steps to Reproduce

                1. Install Jira 8.9.1
                2. Configure the correct base URL
                3. Attempt to connect the Jira mobile app to it.

                Expected Results

                The app connects uneventfully.

                Testing the server-info endpoint via curl reveals:

                ➜ curl --head http://localhost:8854/j854/server-info
                HTTP/1.1 404 
                X-AREQUESTID: 680x587x1
                X-ANODEID: node1
                X-XSS-Protection: 1; mode=block
                X-Content-Type-Options: nosniff
                X-Frame-Options: SAMEORIGIN
                Content-Security-Policy: frame-ancestors 'self'
                mobile-plugin-enabled: true
                push-notification-enabled: true
                instance-name: Jira
                jira-base-url: http://localhost:8854/j854
                is-data-center: true
                X-ASEN: SEN-500
                Set-Cookie: atlassian.xsrf.token=BJLD-I2E2-XZYV-WCHE_4aad390c48c897ed4dc1f0e40ac71645357519ab_lout; Path=/j854
                X-AUSERNAME: anonymous
                Set-Cookie: JSESSIONID=828ADE16F7C117ADFD54DAB9DCCD37EF; Path=/j854; HttpOnly
                Content-Type: text/html;charset=UTF-8
                Transfer-Encoding: chunked
                Date: Tue, 30 Jun 2020 01:20:18 GMT
                

                Actual Results

                A message indicating "Can't connect to your site" is shown on Android and "Can't check compatibility" on iOS

                Testing the server-info endpoint via curl reveals:
                Example 1: Jira 8.5.4, with dark feature jira.redirect.anonymous.404.errors.enabled

                ➜ curl --head http://localhost:8854/j854/server-info
                curl: (7) Failed to connect to localhost port 8854: Connection refused

                Example 2: Jira 8.9.1

                ➜ curl --head http://localhost:8080/server-info
                HTTP/1.1 503
                X-AREQUESTID: 405x9x1
                X-XSS-Protection: 1; mode=block
                X-Content-Type-Options: nosniff
                X-Frame-Options: SAMEORIGIN
                Content-Security-Policy: frame-ancestors 'self'
                mobile-plugin-enabled: true
                push-notification-enabled: true
                instance-name: Jira
                jira-base-url: http://localhost:8080
                is-data-center: false
                new-create-metadata-api: true
                X-ASEN: SEN-500
                Retry-After: 30
                Content-Type: text/html;charset=UTF-8
                Transfer-Encoding: chunked
                Date: Tue, 30 Jun 2020 06:45:22 GMT
                Connection: close 

                Workaround

                The issue is related to a security fix and as a temporary solution this can be disabled by

                1. adding the dark feature flag jira.redirect.anonymous.404.errors.disabled, and,
                2. removing, if present, the dark feature flag jira.redirect.anonymous.404.errors.enabled

                        Unassigned Unassigned
                        rchiquete Rene C. [Atlassian Support]
                        Affected customers:
                        6 This affects my team
                        Watchers:
                        17 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            rchiquete Rene C. [Atlassian Support]
                            Affected customers:
                            6 Vote for this issue
                            Watchers:
                            17 Start watching this issue

                              Created:
                              Updated:
                              Resolved: