Petr Vaníček Expert

It looks really weird and I remember I had same problem some time ago. Try set DEBUG level here (/secure/admin/ViewLogging.jspa) for all com.riadalabs classes and look again into atlassian-jira.log (also look into catalina.out in install folder).

Then try to enable audit log for Insight in /secure/admin/InsightPluginShowGeneralConfiguration.jspa

Hi, did you look into application logs? If there are any errors caused by Insight can you share it?

Hi, it will not be easy to do this. Read carefully upgrade notes for all releases. Main points: * make clone of server as test environment * do everything first on test environment * after every interim upgrade do snapshots and backups Answers on your questions: * There is a lot of changes in GUI, but nothing unacceptable…

Hi, so huw much free space do you have in that partition? Can you free up some space by deleting old backups for example and then try it again (restart app and make reindex)?

Try to set Xms to 2048m Because as minimal value it's small for Jira 8. If you made upgrade from Jira 7 then I think it will be reason. Try it and let me know.

I just check again your screenshots based on your last log and I think I have suggestion. How many custom fileds do you have? What about queries where you are asking for project and some value for any custom field? It will be faster I expect. If you have a log of issues and custom fields then huge queries like "string" or…

Hi, if you have valid maintenace then you can safely upgrade to latest 8.3 version. Only if you have any customizations like groovy scripts then pay attention. But still - try it first on test environment and make backups/snapshots.

Hi, look at WBS Gantt Chart add-on: https://marketplace.atlassian.com/apps/1211768/wbs-gantt-chart-for-jira?hosting=server&tab=overview

Hi, did you try if your elasticsearch is running by Test button in /admin/server-settings?

Hi, Jira Cloud GUI is different in compare of on-premise instances for long time (few years now). What you are linked is documentaton for Jira Server. 

Hi, what about DNS? Can both apps ping to second one by domain name? Are applications running on same or different server? Can you connect from jira to confluence by telnet on app port by using IP (in both directions)?

With calling script I mean this: https://confluence.atlassian.com/bamboo/script-289277046.html You can use one of them - variable or encrypted code in scripts. About encrypting whole line you can inspire for example here: https://linuxhint.com/bash_base64_encode_decode/ So you will encode to Base64 when you will…

Hi, port 8090 is for http, so if you are running it on your local just use http://localhost:8090. If it's not yur case then you need configure SSL for your Confluence ( I recommend use some kind of proxy server). Just follow those articles:…

Hi, please follow this tutorial: https://confluence.atlassian.com/bitbucketserver/connecting-bitbucket-server-to-postgresql-776640389.html

Hi Dmitry, did you try anonym windows? Or you are getting this only after logging in? Because when I try your jira-url/servicedesk I gor normal GUI. Do you have any errors in log files?

Hi, did you made any upgrade? Did you try reindex of Confluence? Or do you have any errors in atlassian-confluence.log file?

Hi, can you share screenshot of part System info (/secure/admin/ViewSystemInfo.jspa) Look at my example what I need to see - if you are using your certificate then just delete part of image where is cert password.

Hi, that's not full part of log with error. But from those few lines it looks like you can't access to PSQL port. Look at pg_hba.conf if it's local DBMS or in firewall if DBMS is running on another server.

Hi, if you are not able to do upgrade then easiest way is encrypt what you need into Base64. I't not secure, but if you encrypt whole line(s) of code then it will not be interesting for someone encrypting everything what can be seen. Another option what I see is calling file system script to which normal user don't have…

You can find this log in HOME (data) folder. Did you try make full (lock) reindex?

Can you try it with new evaluation license from my.atlassian.com?

Hi, probably it should work with downgrade to 7.1.10 because as I look into our 7.13 instance system info there is for jira.downgrade.minimum.version mentioned version 7.1.2. But still the best way for rollback is to use backups of DB and installation a home dir. But I suggest to try everything in test environment before…

Hi, are you using Cloud or Server Jira? If you missing those probably you are using Server version. So only for exporting (info CSV for example) use this article: https://confluence.atlassian.com/jiracoreserver073/working-with-search-results-861257284.html For backup a whole Jira in XML backup use this…

Hi, is it cloud Jira? If yes then Basic auth has been deprecated last year and few weeks ago deprecation peried ended and they start disabling this. Look at this article: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/

Ok, what do you have in Services (/secure/admin/ViewServices!default.jspa)? What about Scriptrunner (/plugins/servlet/scriptrunner/admin/escalationservices)?

I mean those logs below: * INSTALL-DIR/logs/catalina.out * HOME-DIR/log/atlassian-jira.log So if you will log into RDP to server and open browser with http://localhost:8080 then are your problem still appears? What about browser console (in Chrome with CTRL+Shift+i) - did you get any errors like 403,404 or 503 after…

You mean into file or administration screen as I meantion few min ago?

No, add "c.a.j.b.user.search.DefaultUserPickerSearchService" in /secure/admin/ViewLogging.jspa. Here click on "Configure logging level for another package." and choose ERROR as Level.

In that case yes, just add it in Jira in same way and let me know. That isn't error, but debug line.