Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,032
Community Members
 
Community Events
176
Community Groups

JMCA - Error communicating with server

Hi all,

We are migrating from Jira Software Server (v8.22.2) to Jira Software Cloud. 

When we go to the system option of "Migration to cloud" it shows a pop-up with the message "Error communicating with server".

Has anything like this happened to you? Do you know how to solve it?

capture1 (1).PNG

 

We have opened a ticket with Atlassian Support but so far they have not given us any solution.

 

3 answers

1 accepted

1 vote
Answer accepted

Hi!

Looking in the log files we found it was an error while calling a table in the DDBB.

It seems PostgreSQL is case sensitive, so Atlassian support told us to make some manual changes to dbconfig.xml file.

After rebooing the server everything works fine.

Thank you all!

-Patricia

Hello Patricia!
We are facing the same problem.
Can you please share these changes to dbconfig.xml file with us ? Thanks a lot !
Matej

Hello Matej,

I would advise you to open a support ticket with atlassian support becasuse they can give you more details about the actions you have to do base on your specific case.

In our case the issue was tha JCMA was calling a missing schema definition<schema-name> in the dbconfig.xml file. So they advised us to do some manual changes in the dbconfig.xml file and in which line we needed to make the changes.

The change could break your application, so you should ask atlassian support to give you the exact changes you have to make. In our case in took less than a week for them to assist us.

Regards,

-Patricia

Hi @Patricia González 

This is most likely due to network restrictions on your Jira instance. 

Please check with our network administrators if the relevant ports have been opened up on your server hosting Jira.

Jira will need internet access in order to access *.atlassian.net.

For a list of urls and IP Addressed that you can whitelist, please see IP addresses and domains for Atlassian cloud products | Atlassian Support

Hi,

If you Jira Server is behind a firewall, you will need to allow access  domains listed in following page: https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#For-JCMA-plugin-host-communication-

Kind regards

JL

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events