Vickey Palzor Lepcha Expert

@kororos I'd love to know how it has been accomplished - I do upgrades regularly. I have had thoughts of automating it but not sure about where do I start. Are you using some CMS ?

The whole concept of usernames - emails - user profiles , depend on how user management is implemented. Organizations that run their own active directory have the ability to manage everything from Active Directory. By understanding what you did 3 years back, maybe you used internal directory of Confluence - so you were…

How is your organization's user management done in Confluence ?

todos los datos son seguras, pero algunas de configuración va a cambiar :-) 

Go through some known issues too - just yesterday someone reported that he/she was not able to access confluence after upgrade. I have faced one such moment after upgrade - there could be multiple reasons for not being able to access confluence. I for one had issue because of reverse proxy - but as it was one of the known…

Is it running behind reverse proxy or something ? Any errors in log ?

Go with the release note first of all. One more point is do not jump right from 6.0 to 6.9. Take a middle path - upgrade to versions between them. Such an approach minimizes compatibility issues. I would strictly discourage you from making such a huge leap as there are a number of huge releases between 6.0 and 6.9

Are you sure about this ? This is going to be very confusing - what about all the old issues that have already been created and closed. They are all tagged to current username format - you will have to even replace them and that would be pretty risky,

@Varora1406 New Confluence Server Edition is also slowly adapting to new UI - not so much as Cloud though.

My set of advises as I have done a lot of them ; 1) Do it on test environment first 2) Run add-on compatibility check to make sure that your current version of add-ons are compatible with the new version. 3) All your customizations , ensure you move them separately after upgrade - say you've made some changes in server.xml…

Also, if your organization runs Active Directory - you can configure JIRA to communicate with your Active Directory and have users /groups filtered and synced to JIRA. I call it External Users - Internal users are what @Marcos Sanchez has explained you quite well.

You'd want the increment to be uniform ? Say two days increase in Copy Due Date - you'd want to psuh Copy Review Date, Design Due Date Design Review Due Date by 2 days each ?

But you better remove that IP image :p

Good to know David

does your server.xml have ajp connection enabled ? and your proxy server needs to have ajp connection configs too.

And delete all these informations here Adam - has all your IPs of your organization.

I think you are having proxy issue not JIRA issue.

Try this its up and running

Is there any way you can bypass cloudfare and directly try and access jira ? ip and port ?

This issue below - rectify it too , it should not be related to your issue here, but good to rectify it as it causes issues later. 2018-04-27 20:12:12,419 JIRA-Bootstrap WARN [c.a.jira.health.HealthChecks] Your database is using an unsupported collation 2018-04-27 20:12:12,419 JIRA-Bootstrap WARN…

I don't see any issues in the log - some are known exceptions that can be ignored. What error do you see on the browser as you try to access jira ?

You can also check /atlassian/jira/log/catalina.out for log message

atlassian-jira.log attach the whole log here if you can. When you do a start - it check connectivity between jira and db , you can see it in the log.

Can you attach the log message from the section where it validates the Database connectivity ?

Should look something like this ; ........../application-data/jira/plugins/installed-plugins/ Just change the name of the directory installed-plugins and restart

Same server and database is used when you install software on top of core. This is how we run both.

Just rename your installed plugins folder and try a restart .

Did you try restarting " WITHOUT " plugins ?

Hello, Its there with all directories ../conf ../bin ../lib ../jre and so on. -rwx------ 1 uninstall drwxr-xr-x 4 jre drwxr-xr-x 2 lib drwxr-xr-x 3 conf drwxr-xr-x 3 bin drwxr-xr-x 3 work drwxr-xr-x 2 logs drwxr-xr-x 4 temp

I'd always suggest reading release notes and making a decision on how often - but yes, lets not hold on to legacy versions. If you take security or new features into account - I'd say at-least maintain (n-1) pattern with your version and the latest version.