I am project leader for the evaluation of a wiki for our company. Had Confluence running just fine in a test network (not really a network, just an ethernet cable from the server to a switch and into my laptop). Now I wanted to put Confluence in the production network. After changing the Hostname and IP of the server where Confluence is running on I just get a whitescreen when accessing the wiki. Even when I try it over the server directly via localhost:8090 I just get a whitescreen.
Already tried this Solution but that didn't seem to change anything. Even in the forums I couldn't find someone with the same Problem
Hope someone knows a solution to my problem.
Edit: Have to answer like this because of some bs policy which doesn't allow me to post more than once every 24h. Serously Atlassian? Why limit the posts in a Support Forum? What if someone, unlike me, needs instant help and doesn't want to open a ticket?
Hi @Nic Brough [Adaptavist] thanks for replying.
There is no atlassian-confluence.log in my log directory.
Checked the Catalina.out but there wasn't anything noticeable. Just some entries from the 24th of September. But at that time Confluence was running fine without any problems.
Tried to change back the IP and hostname to the former to see if it would work again with no success.
Even when I try it over the server directly via localhost:8090 I just get a whitescreen.
That usually means that the Server container (Tomcat) has started up ok, but that the application (Confluence) has not. Read the application and container logs to see what they are doing.
Atlassian-confluence.log in the <confluence home>/logs directory often has something at the end saying "can't start confluence because...". Also, if Confluence has started but is failing internally, you will find the reason in here.
Catalina.out in the <confluence install>/log directory is where to look if the application log doesn't tell you anything usueful
They have a spam problem with people/bots posting hundreds of questions and hence generating lots of email. As your karma rises, you'll find your account gains privileges (quite quickly - once you've got in a couple of questions, comments, answers or a few votes, you're pretty much free to post as much as you like) If there's no atlassian-confluence, that really strongly implies it's not run the application at all. But that should be stated in Catalina.out. Check for other logs in both directories as well.
While you try to check what might be causing this issue, you can also consider checking if the user running Confluence does have the READ/Write permissions to the Home folder and also the Installation one, since we can see that Confluence is not being able to start.
Another alternative would be to check if all the parameters are linking properly to the database through the confluence-cfg.xml file locate in the Home folder of the instance.
Hope it helps ya!
Checked all the logfiles ant the confluence-cfg.xml. Didn't notice anything in them. I ended up setting up the server from scratch because i don't have the time for searching the problem cause all week long. Thanks anyway for the help.
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events