The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Problems installing Jira on my own server (Hetzner)

Niklas Petersen
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!
October 20, 2020

Hi,

first, it worked fine, and I was able to trigger the "registration phase" with my trial account, but once that was about to finish, Jira shut down and I can't restart it?

My setup:

Software: Jira-Software
I use this container to install the software.
https://hub.docker.com/r/atlassian/jira-software

Server: Hetzner Cloud
I switched from CX11 to CX31 after it shut down, as I thought maybe 1 VCPU and 2GB Ram was not enough. But I still have the problem.
server_config_hetzner.png

Docker Container Log:
container_log.png

Docker ps:

 

docker_ps.png


If I visit "http://<domain>:8080/ I do not get any response. Before, I was able to register my trial key there. Or is it running somewhere else? What did I do wrong? :(

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Daniel Ebers
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 Champions.
October 27, 2020

Hi Niklas,

welcome to the Atlassian Community.

To be honest, it is impossible to tell from here - the logs show nothing unusual. There are only entries of severity "INFO" - this is just fine.

By looking at the specs - 1 vCPU and 2 GB RAM - it is not that much but for a test drive it should suffice.

Next step would be to investigate further, possibly from atlassian-jira.log why it is not reachable.
If you share more details somebody here in Community is possible able to say more to the problem.

Cheers,
Daniel