It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

HTTPs not starting after underlying system restart/shutdown


I am hosting a containerized Confluence (server) v7.0.1 configured with HTTPs and its own certificate on a server. The Docker image that I am using is atlassian/confluence-server.

All works well until I have to shutdown/restart the server. If one of those 2 operations are required, the HTTPs Confluence is not starting by default - just HTTP. After the server is booting up, Confluence is accessible via HTTP, but not also the HTTPs.

The workaround that I have found was:

- Delete the /var/atlassian/application-data/confluence/lock file;

- Change the port mentioned as "THIS PORT" with a new port in /opt/atlassian/confluence/conf/server.xml row <Server port="<THIS PORT>" shutdown="SHUTDOWN">

- Stop and start again Confluence /opt/atlassian/confluence/bin/ && /opt/atlassian/confluence/bin/

I would like to avoid this operation in the future as it takes a while until I have Confluence back again with HTTPs enabled.

Is any way that I can solve this issue?

Please let me know if you need any additional information.


Best regards,


1 answer

You can add Confluence as a service. This is usually done as part on the installation process - there is a prompt if I remember...

Otherwise, you can add the start/stop script in /etc/init.d. Here is an example that was generated as part of the installation process for JIRA. Just change to reflect your installation (I have removed the actual installation path


# JIRA Linux service controller script
cd "/<jira_installation_path>/bin"

case "$1" in
echo "Usage: $0 {start|stop}"
exit 1

@sukkeong thanks for your reply. In the containerized version, I have not seen any prompt to select installing Confluence as a service.

I would prefer a fix with a configuration in UI or in some files rather than fixing it with a cronjob. For some reason, if I am doing all these changes from the ticket's description too fast, I am getting this strange error:

23-Feb-2020 09:23:29.122 WARNING [Catalina-utility-4] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-jsse-nio-8443-exec-9] (id=[248]) has been active for [69,478] milliseconds (since [2/23/20 9:22 AM]) to serve the same request for [https://localhost:443/plugins/macrobrowser/browse-macros.action?detailed=false&macroMetadataClientCacheKey=1582448914693] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [3] thread(s) in total that are monitored by this Valve and may be stuck.

Therefore, beside calculating the threshold until I can trigger a cron-job with all those steps inside, I would prefer a fix in UI or in some Confluence files.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Confluence

Lessons and Learnings: Six Months of Working Remote [Discussion]

Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...

4,120 views 4 6
Join discussion

Community Events

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

Events near you