Alexis Robert Community Champion

OK so this is actually a network issue, you should ask your network administrator to change the routing so that the Jira instance does not have to go through the proxy to call its own IP.

OK so you can try bypassing the proxy by calling the internal IP directly : change your /etc/hosts file to point your Jira DNS to the local IP : 127.0.0.1 my.jira.com 

Hi @James Jing , you should do a backup of your Jira instance, and then import it in your new Jira on AWS. Let me know if this works, --Alexis

I can see that curl is using a proxy : * Connected to proxy.zz.zz.com (xx.xx.x.xx) port 8080 (#0) * Proxy auth using Basic with user 'username' You should also configure the proxy in Jira, as described here : https://confluence.atlassian.com/jirakb/configure-an-outbound-proxy-for-use-in-jira-server-247857187.html And then…

Hi @Akshatha , you can have a look at . this KB : https://confluence.atlassian.com/jirakb/how-to-fix-gadget-titles-showing-as-__msg_gadget-813697086.html/?_ga=2.73076308.696304845.1573393740-1867168444.1563630283 Also, can you try from the server to call its own url ? You can try this : * From the Jira server itself, Jira…

Hi @Alicia Olson-Gwaro , I would advise upgrading to Jira 8.5.1 as this is the latest Enterprise version. You can read more information about Enterprise versions here : https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html Let me know if this helps, --Alexis

Hi @svaddeman , this file should be created manually if it doesn't exist yet on your instance. let me know if this helps, --Alexis

Hi @Omprakash Thamsetty , this documentation provides compatibility matrix for the Application Links between Atlassian products : https://confluence.atlassian.com/applinks/application-links-version-matrix-779174762.html#Applicationlinksversionmatrix-table2 You will be fine as most of your apps are fairly recent. Just make…

Hi @Oliver Nickelson , as you can see from this page : https://confluence.atlassian.com/cloud/storage-for-jira-and-confluence-873871366.html The storage is mostly the attachments, the number of issues etc likely are only a few GB at most. Let me know if this helps, --Alexis

OK I see, in my case I've worked on Data Center where Apache was used as a load balancer and reverse proxy, so there were no issues of traffic between 2 separate components.

I think it's very tricky to modify the XML backup - no idea of the side effects this could have.

In this case I would recommend disabling the internal Confluence backup job, as per Atlassian official recommandation on this page : https://confluence.atlassian.com/doc/production-backup-strategy-38797389.html Although Confluence provides a scheduled XML backup, this backup method is only suitable for small sites, test…

Hi @Snorre Selmer , it is not recommended to perform internal backups like these on a production instance, because these will take a lot of time as you get more content on your Confluence instance. The best practice is to disable this job, and instead do a backup directly on your database. This is much better in terms of…

Hi @Christopher Lankow , I think the problem here with Data Center is that a lot of synchronization happens between the nodes as they have to keep a lot of information shared between them, and adding as additional layer with SSL could potentially degrade performance. But if you think your network is robust enough, then you…

Hi @ravi , for this version, you can do a direct upgrade. There is no need for an intermediate upgrade. I have done one myself last week and it went without any issue. Make sure to upgrade all your addons before, and follow this guide to upgrade…

in this case you need to do a full backup import, and this will erase your Jira Cloud settings. I don't think there is a way to achieve what you want without deleting all your project configuration in Cloud

Yes it should be this query. I think for SQL Server you can also do this directly in the interface too.

Sorry, your post is tagged as "Confluence", did not realize it was for Jira. In this case, the correct collation is Latin1_General_CI_AI. You should setup a new empty database with this collation, then run the data import.

Yes you're right, at the moment this is a limitation on filters.

If you just reimported the data on SQL Server, the database will keep its collation. Did you try to backup the data from Jira with the XML backup, then setup a new Confluence that points to the empty database, and import it using the Confluence wizard ?

Hi @Maikes , there is no bridge, "LDAP" is the type of connection, but it connects directly to your AD.

Hi @Maikes , to connect to your Active Directory, you can follow this documentation : https://confluence.atlassian.com/doc/connecting-to-an-ldap-directory-229838241.html LDAP is the protocol used for the AD connection, you just need to configure this in your Confluence administration. Let me know if this helps, --Alexis

Hi @Bart Scholtens , what you can do here is to export your Jira server issues to a CSV file and then run the import wizard with that CSV on your Cloud instance : https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html This way you only import the issues, and you can manually fix any problems…

Hi @Patrick Vogt , yes you're right, another issue has been identified with some instances being slow : https://confluence.status.atlassian.com/ Atlassian is investigating and will provide more information during the next hour. Thanks for your patience !

You're welcome @Leif Gringmuth ! Please remember to mark this issue as "Accepted" so that other users can find it later :)

You're welcome ! Please remember to mark the answer as "Accepted" so that other users can find it later :)

Hi @Rami Smolyar , this should be resolved now as Atlassian claims they've fixed the issue.

Can you check your logs and look for lines starting with ERROR ? The one you attached on your first post is only a WARNING and might not be related to your issue

Hi @Bruce Caldwell , if you've already migrated the DB to SQL Server 2016, then you can just run the 8.5 upgrade then : no need to backup and re-import the data !

Hi @Leif Gringmuth , there is an ongoing incident for several Cloud products, as you can see here : https://jira-service-desk.status.atlassian.com/. This is why some instance are slow this morning. Atlassian is working on the issue and it should be resolved soon. Let me know if this helps, --Alexis