Alexis Robert Community Champion

You can actually use the same Server ID as your production server, it's only used to generate the key - it doesn't mean that the licence is tied to a specific server.

Hi @Fabian Pohlmann , you don't need a separate Starter Licence for your testing instance : you have a free developer instance with your current production licence, you can find it on your my.atlassian.com, click on your Jira licence and you will see a "View developer License" button below the key. Let me know if this…

Hi @Luc PHAN , at the moment the Cloud version only lets you choose the beginning of the domain : mycompany.atlassian.net

Hi @Luc PHAN , it's very simple : if you're accessing the Confluence instance with a URL like xxx.atlassian.net then you're on the Cloud version. Otherwise, it's the Server version. Let me know if this helps, --Alexis

OK I get it ! in this case you can use this add on : https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira It will help you copy settings from one instance into the other.

Hi @Eric Schreiber , there's an easy way to do this : perform an SQL dump of your Jira production database, and import it into the testing one, you'll find all your settings/issues/projects etc. You'll only need to change the instance Base URL after starting it for the first time and that's it. You can also do a XML backup…

You can use this plugin for example : https://marketplace.atlassian.com/apps/22929/copy-page-tree?hosting=server&tab=overview Copy the full tree of your spaces into a new space and export it, and that's it. This plugin can be tested for free for 30 days.

Hi @Akop , you can find on this page how to automate Cloud backups : https://confluence.atlassian.com/jirakb/how-to-automate-backups-for-jira-cloud-applications-779160659.html?_ga=2.264365256.696304845.1573393740-1867168444.1563630283 Let me know if this helps, --Alexis

Hi @Sekhar Chandra , you could simply try to change the space settings in server A : change the space name and key, this way you won't have an issue when importing in server B. Let me know if this helps, --Alexis

You're welcome ! Please remember to mark this question as Accepted so that others can find it later :)

Hi @Joseph Joy , yes you're right - sorry for the mistake :) The link I provided stil lapplies though : you 'll find there how to move from Next-gen to Classic, and basically all the manual actions I listed still apply : you'll need to recreate some settings if you have a heavily customized next-gen project.

Hi @Joseph Joy , it's possible to change from classic to next-gen, this documentation has all the steps to do it : https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html But if you have lots of customizations (Board statuses, issues types, customs fields ...) you…

Hi @Mahdi Challouf , this page from the Atlassian documentation should have all the info you're looking for : https://confluence.atlassian.com/jirasoftwareserver/jira-server-mobile-app-966063511.html Basically, you will be able to access your Jira Software projects, it's fine if you're using a VPN and SSO. But you won't be…

Hi @kuang5 , yes you're right, that must be the issue. Let me know if switching to 64 bits fixes the issue for you !

Hi @dotan goldberg , the best way to migrate is to do a XML backup in Jira, then remove the dbconfig.xml file in JIRA_HOME and restart Jira : you will then be able to enter the settings for your new database, and the next screen will provide a way to import your XML backup. For the database, you can use either PostgreSQL…

Hi @Magnus Tamm , the other option you have is doing a XML backup from your Confluence instance : this will give you a zip file that you can then import into another local instance. The documentation for this can be found here : https://confluence.atlassian.com/doc/manually-backing-up-the-site-152405.html More information…

Hi @Magnus Tamm , Confluence backup should be done on database level, this is where your data (pages, spaces, configuration, ...) is stored. Let me know if this helps, --Alexis

Hi @Andrew Gorman , is it a requirement to have SSL between your aplications links ? If it isn't, you can follow this documentation to setup a simple connector to bypass your proxy and make a direct link between your applications…

Hi @kuang5 , Confluence 7.0.3 supports AdoptOpenJDK, so there's no problem here. Also, only AdoptOpenJDK 8 or 11 is supported by Confluence, no need to try other versions. I would suggest that you remove the old Oracle JDK, just in case. For your issue, there's definitely something wrong with the version of Confluence…

Did you download the Linux installer (or tar.gz archive) from https://www.atlassian.com/software/confluence/download ?

This is definitely because you're not using the right biinary for your server. Can you check what's the output of "uname -a" on your server ?

Hi @kuang5 , looks like you're getting this error because you're using the arm version, for Linux the correct version is this one : https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/download/jdk8u232-b09/OpenJDK8U-jdk_x64_linux_hotspot_8u232b09.tar.gz Let me know if this works, --Alexis

Hi @Benoit Bouffard , you can ask Atlassian Support to change this for you : https://support.atlassian.com/contact/#/ Let me know if this helps, --Alexis

Hi @Sebastian Benz , yes it's possible if you allocate enough resources to the server. That's why it's usually recommended to have applications running on different servers, so that an issue on Confluence won't impact your Jira Service Desk instance. But in the end, it's totally up to you to decide how you want to organize…

Hi @LEM , at the moment Confluence is not compatible with Oracle 19c, however there is an open ticket that you can follow for this : https://jira.atlassian.com/browse/CONFSERVER-58364 You can vote for this issue or comment on it if you want this to be prioritized :) Let me know if this helps, --Alexis

Hi @JDave , you won't have access to Dashboards, but you can access Kanban board for example. You can then move issues on the board etc. Let me know if this helps, --Alexis

You should try removing the proxy settings in Jira, and ask your IT team to change the network rules so that the server can call itself.

Some gadgets need to probably call themselves and others not ... but I see your point.

Hi @James Jing , you just need to do a XML backup in Jira : https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html Then, setup a new VM on AWS and copy your existing Jira Home and application directories, and delete the dbconfig.xml file in Jira home. Start Jira on AWS, and setup the database…

Hi @Vishal , this message means that your instance is running out of free memory. You should consider upgrading from 2048MB to 4096 for instance. You can see detailed steps here to change the JVM memory settings : https://confluence.atlassian.com/adminjiraserver/increasing-jira-application-memory-938847654.html Let me know…