Alexis Robert Community Champion

Hi @John Chuma , I usually give 2 options when asked about SSL certs: * the cheapest way is to use Letsencrypt, as they provide free certificates. The certs are only valid 3 months but it's very easy to automate. * the easiest way is to simply purchase a cert with Digicert, GlobalSign, Geotrust ... or anyone you like, that…

Hi @Schups , it's pretty much the same, the only difference is that the KB explains how to do this directly in MySQL with ALTER statements, where you went for a more manual approach with the find/replace in the dumps. But in the end, pretty much the same yeah.

Hi @Schups , there is actually an Atlassian documentation page that explains in detail how to do this: https://confluence.atlassian.com/kb/how-to-fix-the-collation-and-character-set-of-a-mysql-database-744326173.html Keep in mind that this is quite complex and should be done by your database administrator if possible.…

Hi @Schups , I believe utf8mb4 is only to support emojis - if you don't plan on using them, you can keep the current charset and Jira will work fine with these settings. Let me know if this helps, --Alexis

Hi @Schups , this setting is only for post-upgrade tasks as its name implies: * upgrade.reindex.allowed=false So you don't need to worry about changing it - it can stay like this as it only affects upgrade operations. Let me know if this helps, --Alexis

When you get your clone up and running, you can also try some debug from the command line as explained here, I find this very helpful as it helps narrow down the problem when dealing with certificates. 

Hi @Tim Menke , when you say that "HTTPS doesn't work after the upgrade", do you mean that you get an error when trying to access your instance with https://jira.company.com or do you get an error in the logs ? This is the first step to be able to help you so can you provide more details on the error message or logs that…

Hello @Nicolas Tizeira , the server ID is only used to generate the licence key the first time, you should be able to use the key on any server after it's created. There might be another issue preventing the key being used: are you sure you're using the key for the right component ? It will not work if you try to use a…

Hi @Pierre Walsh , you could also change the sort order of the comments to show the newest first, as explained in this page. Let me know if this helps, --Alexis

Hi @Staffan Sandberg , you can check the Supported Platforms page on Atlassian website: it doest not list MySQL 8.0 as compatible with Jira 8, so you'll have to use MySQL 5.6 or 5.7. Let me know if this helps, --Alexis

Hi @saif-mahmud , the only error I see here is " Startup check failed. ", there is nothing else in the logs. Can you give a bit more details on how you did the upgrade ? What steps did you follow ? Thanks, --Alexis

Hello @Muhammad Imam , yes this is possible, it will work fine this way. --Alexis

Hello @Dimitri , yes this is exactly how you need to proceed: take a XML backup of your existing Jira instance, and restore it in your other server that is empty. Let me know if this works, --Alexis

Hi @Dimitri , I would recommend upgrading to Jira 7.13.1 as this is the Enterprise Release. You can upgrade directly to this version from 7.3.2. I usually use the manual procedure. You will basically backup your data, create a new database, point the new Jira instance to it, then select to import your data. Let me know if…

I don't think so as Datacenter doesn't have limits on the number of nodes, so it shouldn't change for a Developer licence.

Hi @Christian Genette , I've actually had the exact same issue a few days ago, and this is what fixed it for me (Atlassian support actually provided this answer): Let's first try starting JIRA with the correct encoding and verify if it helps. Please start JIRA with the variables : -Dfile.encoding=utf-8…

Hi @Balaji J , as stated in this Atlassian page, you can very well use a Developer licence for your Datacenter instance. Let me know if you have any questions, --Alexis

yes that's weird, I don't see anywhere port 8443 in your output. Maybe you can try restarting the server just in case ? 

Hi @burak.turgut , did you follow the Atlassian documentation when implementing SSL ? I think at least your "server.proxy-port=80" is wrong and should be server.port=8443 Let me know if it works, --Alexis 

Hello @Muhammad Imam , you can't synchrnize your data between today and 5 days later. You will need to stop your current Jira instance, do all the upgrade and migration steps, and then start the production again. 

Hi @Alvin , this Atlassian documentation has all the information to migrate from Cloud to Server. Let me know if this helps, --Alexis

Hi @Muhammad Imam , you will need to first upgrade to Jira 7.0.11, this page can help you. Then you will be able to upgrade from Jira 7.0.13 to Jira 7.13.1, this documentation is perfect for this. For your database upgrade, you will need to perform it after the first upgrade step to Jira 7.0.11, you can follow this…

Hi @Alvin , there is no specific documentation for Jira 7.2 because there is no need for it - it's all the same for all 7.x versions. Basically, once you've done a backup of your database and JIRA_HOME, you simply point the new binaries to your existing JIRA_HOME and start Jira. Of course you should first test this on your…

Hi @Priyanka Karguppikar , all the instructions to implement SSL for Jira are available on this page. Let me know if you have any questions, --Alexis

Hi @Alvin , you can have a look at the Preparing for upgrade page that will help you with the operation. From 7.2 I believe you can do a direct upgrade to 8.0.1. Let me know if you have any questions, --Alexis

Hi @Digi Vine , do you at least get the box to paste the licence when you click the link or nothing happens ? Have you maybe tried with another browser ? Otherwise, you will need to check the application logs, this page explains how to get the logs. You will need to connect to your server to get those. Let me know if you…

Hi @fareed nema , well the bin file is the installer, so that's it :) You should now try to navigate to the Health Check menu and see what is reported here. The URL should be http://MyJiraDomain/plugins/servlet/troubleshooting/view/

Do you know if you used the installer or the archive file ? This will help understand what is wrong with your instance.

Hi @fareed nema , there could be a few things that cause this issue, perhaps you can give us more details on how you installed Jira: is it with the installer, or the archive file ? Can you go to the Health Check menu and see if any errors are reported here ? You can follow this documentation to find it. Let me know if you…

Hi @Conan Moriarty , what exactly is the issue in applying the licence ? You should be able to navigate to the Licencing menu and just put your key, as shown in the documentation here. Let me know if you have any questions, --Alexis