Jira & Confluence integration. Confluence macro jira-issues displays "The host did not accept the connection within timeout of 10000 ms"

jira and confluence are on the same host behind the apache, there are public DNS names

https://<DNS>:port1 for jira

https://<DNS>:port2 for confluence

Thare are applinks created on jira for confluence and on confluence for jira

Bor both Outgoing Authentication setup as 'Trusted Application'

I put on confluence page 2 macro:

jira-issue

jira-issues

Thare are following issues:

1) When user clicks jira link (jira-issue) - jira shows login page (instead of auto login as Trusted Application)

2) jira-issues marco show 'The host did not accept the connection within timeout of 10000 ms'

Thanks for any help in advance

6 answers

1 accepted

After we start using different DNS names for jira and confluence problem is dissappeared

0 vote
Janet Albion Atlassian Team Mar 06, 2013

Hi Alex,

Just a quick question here.

1) When user clicks jira link (jira-issue) - jira shows login page (instead of auto login as Trusted Application)

does the user that click on the JIRA link has user account in JIRA instance ?

2) jira-issues marco show 'The host did not accept the connection within timeout of 10000 ms'

Since JIRA and Confluence running in the same host:

  • does the integration works with Trusted Application created using http://localhost:port_number instead of using the DNS
  • does the integration works if you use HTTP connection instead of HTTPS connection ?

If you decided to keep using any of the connection, make sure to Edit the Display URL in the Application Link.

Hello Janet.

does the user that click on the JIRA link has user account in JIRA instance ?

yes, jira and confluence has the same users - they are from ActiveDirectory

does the integration works with Trusted Application created using http://localhost:port_number instead of using the DNS

does the integration works if you use HTTP connection instead of HTTPS connection ?

no, I've tried local addresses on HTTP -result of jira issues macro is "The jira server was not able to process the search. This may indicate a problem with the syntax of this macro. Alternatively, if this macro is requesting specific issue keys, you may not have permissions to wiew one of these issues."

jira issue macro works the same way: When user clicks jira link (jira-issue) - jira shows login page (instead of auto login as Trusted Application)

Probably this is linked problem: the same user can't be logged the same time in both jira and confluence:

user logins into jira, then in new tab logins into confluence, if user returns to jira - application says "You not logged in", after login in jira, goes to confluence tab - application says "You not logged in".

I have faced the same problem. The cause is the firewall issue. Once you release the firewall on JIRA side, you might not face the same problem. Or you open the JIRA port in the firewall setup for inbound rule.

Now I have "Unable to retrieve the application's certificate: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake" both on jira and confluence when I try to enable Incoming authentication

thanks in advance

Sounds like a certificate validation issue. Do both your applications have the same SSL certificate or does each one present a different self signed certificate? If the latter is the case each will reject the other because they don't match.

Just re-reading your original post I have a question. Where are you terminating SSL? Apache or Tomcat? The point of using Apache to reverse-proxy in front is then you don't need to access the applications on different ports. You should be using proxypass and proxypass-reverse to get traffic to/from the tomcat instances and the client on the Apache port (80/443). It should also terminate the SSL presenting one certificate for the server. If all three are on the same machine you can argue that SSL between Apache and Tomcat is redundant.

Continuing the topic:

Where are you terminating SSL? Apache or Tomcat?

Actually SSL is being terminated before application server, so the problem most likely is: JIRA addresses Confluence signing request with trusted certificate, but nor apache, nor confluence can't decript it, because they don't have private key for this cert.

So the solution for our intranet users would be http applink, but users from outside local network will recieve an error, mentioned earlier by Alex.

I'm currently looking for the way to route requests from both applications, stationed on same server as external request to pass through server, that terminates SSL,Some bright ideas on how to do it, or maybe better options on how to solve this problem?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Friday in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

296 views 11 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you