Not quite. Read the title of your question - you said you were unable to log in, then it was fixed by restarting it. The body describes the failed logging in, but your title says it's fixed.
Anyway, I assume what you mean is that the restart does NOT solve the problem, and you still cannot log in.
Am I right in assuming that after restart, you visit with a browser and get the login screen ok? Then nothing else? Is there a Jira header at all, or is it really a blank page?
Can you check what html is coming through on the blank screen? Ctrl-U in will open the raw html - doesn't matter too much what it is, but it might be helpful to know if it's a tiny amout or a huge block that might actually be correct.
And, again, what does your log files say?
The restart does solve the problem, but my concern is about why the issue is occuring in the first. place. The screen renders without any noticable html issues and the login screen always shows up fine.
Atlassia-jira.log contains 53,567 lines....I'm not sure where to begin with it.
So what conditions prompt this inability to log in? How often does it happen and lead you to have to restart?
If the screen is rendering without issue, then why are you not able to log in? What does the user see? An anonymous access (no name top right). The "html is ok" kind of contradicts "can't log in"
The log file - look for errors or warnings, especially login ones!
The "conditions" prompting the inablity to login seem to be nothing more than time passing. It's happened twice now...perhaps once a week.
I see some ldapo errors in the logs...will need to dig into these further yet.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG