When I go to it, there is the typical login to enter username and password. I enter these and it looks like it's loading, but it just blanks out the page. I know it's recognizing it because if I enter a wrong username of password, I get an error.
Does anyone know where I can track down what's going on? I don't see anything in catalina.out or catalina.<date>.log.
Our solution was to fix the connector settings in server.xml since we used an URI that was not reachable. Since our staging confluence accepted the login, it would redirect to the configured URI, that was not existing.
after we corrected our proxy and DNS settings everything worked fine.
Not really, at least not where I could say that I have a solution.
I eventually gave up and just ran the update on the production environment. When there were new updates for both Jira and Confluence, I rsynced -av the environments to the staging server, loaded the current database, and tried again.
This time, neither of the scripts in /opt/atlassian could read /var/atlassian/application-data. I eventually deleted all of the atlassian files, made sure that all directories that they were in had global read and wright privileges, rebuilt the evaluations, and tried again.
That worked. I guess the answer is to trash everything and keep trying until it just works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Team members are employees working across the company in a wide variety of roles.
July 3, 2020 edited
Hello Chris,
Thank you for raising this with us. Does this happen for all users, or is this the only user on the site?
I would recommend instead of looking at the Catalina.out logs, have a look at the Confluence Server logs and see if you can find any hints about what might be happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.