Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

After reboot get ERR_TIMED_OUT errors

Ashley Hughes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 9, 2017

On a new install after rebooting the server running Confluence I can't get back to https://ip:8090

Firewalld is set to allow port 8090, confluence service is running. Nothing crazy in catalina.out

Not sure where to start this is a new install on Centos 7 two vCPU and 8GB, Postgresql db is running on another VM

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 9, 2017

That suggests that Tomcat is running ok, but it has not started the application internally.

Check if it is Tomcat/Java listening on 8090 with a "netstat -plant" and then look at the Confluence application log to see why it's not starting (<confluence home>/logs should contain several logs, start with the atlassian-confluence.log )

Ashley Hughes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 10, 2017

Of course it starting working of its own accord!?!

Think I might not given the database enough time to fully load before starting the confluence vm. Thanks for the info

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events