nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JMCA - Error communicating with server

Patricia González_9hy1yp

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.

Comments

JL_868g03

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

Deon Meyer

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

Patricia González_9hy1yp

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

Matej Štrba

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

Patricia González_9hy1yp

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud-migration

cloud-migration-assistant