Why do I keep getting a 404 "Oops, you've found a dead link." with JIRA 7.4.3 REST API?

I'm using JIRA Server 7.4.3 on a localhost on port 9000 with the default embedded database configured.  I can access JIRA dashboard and create tickets, etc. with http://localhost:9000.

However, when I try to access the JIRA REST API to examine a ticket I created with an ID of 10000 using the URL http://localhost:9000/jira/rest/api/2/10000, I get the 404 "Oops, you've found a dead link." error.  It seems I cannot access the REST APIs no matter what I do.

I've tried searching for days whether there are any configurations I need to set but from everything I could find, the REST APIs are configured to work by default in JIRA 7.

Can someone let me know how I can enable the JIRA REST APIs in my configuration as described above?  Thank you.

2 answers

2 votes
Gaston Valente Community Champion Sep 01, 2017


I think that the correct URL for the service you need is


In your case


I can't believe I overlooked that!  Thank you very much for pointing it out.  When I entered the following URL into my browser:


I got what I expected as a response:



Thank you very  much for pointing out my error!

Gaston Valente Community Champion Sep 03, 2017


Gaston, may I ask one more question regarding the Atlassian SDK for plugin development?  I downloaded the latest version from the Atlassian download site yesterday.  I installed it using all the defaults including port 2990 and it appeared to install without issue.  Running atlas-version in a Windows Powershell window displays the appropriate information.  How can I test it in a browser to ensure it installed properly?  When I provide the URL, http://localhost:2990/jira, I get a "Can't reach this page" error from the browser.  I'm hoping I've overlooked something that's as simple as the previous question I had. 

One of the many joys of having ADHD is that I have grand visions that are quite creative yet fail miserably in practice because of lack of attention to details!  :)

Thanks again for your help on the previous question!  Looking forward to your response.

Never mind!  I finally found the answer....I needed to simply run a standalone version of JIRA first with the following command:

atlas-run-standalone --product jira

That seemed to do the trick.

Marking this issue as solved.  Thanks again!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,729 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you