Dear all,
We are facing to a wierd issue with Jira 10.x and Exalate plugin. Let me describe the scenario and hoping that some of your could help or have an idea how to solved
We have the following VM structure which have not change
Jira On promise ( WIndows server 2022) => lets call it JIRA_A
Jira Out on premise ( WIndows server 2022) => lets call it JIRA_B
Actuall situation :
On Jira_A and JIra_B we are running Jira 9.12.15 and Exalate 5.22
When change occurs in JIra_A, they are sync on Jira_B wich then sync it out to our customer Jira Cloud through a PROXY server.
From our PROXY Server , all communication is open and cloud url is fully open
Result :
Under this config all is working fine without any trouble in communication through a whole chain
Problem situation :
Due to Atlassian security , we must upgrade our Environement to Jira 10.x and the compatible version of Exalate.
After doing such upgrade, exalate is not any more capable of communicating with the Jira cloud from the JIRA_B.
We receive a “Communication time out error to the exalate cloud url”
Please note that during that, our VM architecture has not change at all , even at the proxy side
IF we simply roll back to previous version then it works again.
Conclusion : There seems to be really an incompatible issue with Exalate and Jira 10.x at some point in such configuration
Does anyone face such situation or have any idea where to investigate ?
We have make a remote session with Exalate support team and so far they are still investigating and have no idea
Thanks for sharing any suggestion
regards