Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Base URL fail. http://xx.xx.xx:8080/secure/Dashboard.jspa is blank.

Hi everyone,

JIRA is not able to access itself through the configured Base URL

I have a fresh Jira 7.3.8 installation. No proxy, no apache. Fresh ubuntu 16 + fresh jira. All pages are accessible exept for /secure/Dashboard.jspa.
It hangs with a white page. I came through many sugegstions but all of them concern certificates and SSL, but I before I start configuering SSL I want simply access dashborads from :8080.
Maybe that's some ubuntu security settings?
Can you please help?


ERROR [] An error occurred when performing the Base URL healthcheck:
org.apache.http.conn.ConnectTimeoutException: Connect to xx.xx.xx.:8080 [/xxxxxxxx] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(

Caused by: connect timed out

1 answer

1 vote

It is what the error says - the server cannot reach itself over the base url you've given it.

This usually means you've got a misconfigured network, or a firewall on the local machine that blocks access from xx.xx.xx.xx to xx.xx.xx.xx on port 8080.

Check the firewalls and that /etc/hosts is correctly referring to localhost and your ip address if it's in there.

A simple test on the server is to try the command line:  telnet xx.xx.xx.xx 8080 will try to open a connection on that port and might give you a more useful error message.

Thanks Nic for the prompt reply. I'll get our nework team to sort it out. Meanwhile I was successul to "wget" with response 200, but "wget my-host-ip: 8080" ends up in "failed: Connection timed out. Retrying." 
But jira is fully accessible from the DNS name, it is just long, ugly AWS name.

Sounds like my-host-ip is not set up correctly

Suggest an answer

Log in or Sign up to answer

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