Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trello and Android App cannot connect to Jira server

Roman Lemtugov July 5, 2020

Hey there.
After installing jira on Server:
Centos 8, 
NGINX 1.16.1,
PostgreSQL 9.6,
Certbot (Let'sEncrypt)
SSL Cloudflare (Full (strict)Encrypts end-to-end, but requires a trusted CA or Cloudflare Origin CA certificate on the server)

I can get access to my jira in browser, but cannot in jira android app.

Installed on Jira

  • Trello Connector for Jira Server
  • Advanced Roadmaps for Jira

  • BigPicture

All needed plugins are anabled, like Jira Mobile, Mobile Plugin for Jira etc.

NGINX configured based on atlassian tutorial. Jira is availabe in all browsers including mobile.

Issue with Mobile App

In Android browser
photo_2020-07-05_16-20-57.jpg

After clicking "Open in app" or oppenning app and putting my jira URL
photo_2020-07-05_16-24-49.jpg

Find out some potential problems, tried all of them except 
https://confluence.atlassian.com/jirakb/problems-with-logging-in-because-of-missing-headers-or-cookies-981146624.html

If the problem with header or coockies, how to implement a solution on NGINX?
If the problem with Cloudflare, how it should be configured in my cloudflare account?



Issue with trello connect
Always have only this pop-up without any actions.
As result cannot connect Trello to my jira server

Image 006.png
Please advise how to fix both issues.

Sincerely,
Roman


1 answer

1 accepted

0 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 10, 2020

Hi Roman,

Unfortunately there is a known bug with the Jira mobile app and Jira Server 8.10.0. The bug causes the mobile app to display the "can't connect to your site" error in your screenshot. Details of the bug are on our public Jira instance: JRASERVER-71217 

Fortunately there is a documented workaround, which you can apply now:

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

(the links provide instructions on how to specifically apply dark features)


Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.10.0
TAGS
AUG Leaders

Atlassian Community Events