404 Oops, you've found a dead link.

Hello, after adding 2-Factor Auth Secure Login to Jira, we get 404 Oops, you've found a dead link after entering PIN

5 answers

It is usually caused by plugin cache. 

Please perform the following to see if the issue is fixed:
1. Shutdown JIRA
2. Delete the following hidden plugin cache directories: 
1) JIRA_HOME/plugins/.bundled-plugins
2) JIRA_HOME/plugins/.osgi-plugins
3. Restart JIRA (These directories will be recreated on JIRA reboot with new plugin cache)

Dear Mahibur,

sorry for the inconvenience with that. There sneaked a little bug into the plugin. In result the forwarding mechanism after entering the pin successfully, results in the 404 error message. This happens especially on instances without the JIRA or confluence context in the URL.

A fix for that is already developed and currently be tested. So I am confident, we will provide a bugfix release in the next days.


Thanks Alexander, can you help with the HTTP Status 400 error - The request sent by the client was syntactically incorrect?

This only happens to some users.

Hi Alexander,

we are facing a similar problem. After successfully entering a pin we get redirected back on the same page to re-enter the pin with target the Logout page, which doesn't make sense.


Any chance fro a fix?


We are facing the same error however it is right after we click "Export project".

Is there anything we can try? Is there a new version?

I have installed the plugin and clicked the link and that's as far as I can get in my testing. smile

Kind Regards,


Apart from my Admin account all users get a HTTP Status 400 instead of the prompt to add PIN, can anyone help?

We released Version 1.2.1 of Secure Loin for JIRA on Tuesday. It should solve the problem with the 404 messages after entering the PIN. It had been a problem with the URL forwarding in certain circumstances. But now the plugin uses relative URLS for the forwarding, and in all reproducable situations this version fixed the problem.

I know this is old, but had a similar issue when I upgraded from 7.12.0 to 7.12.1; found that the Context Path was dropped in the upgrade for some reason. I also cleared the paths mentioned above and didn't appear to help, but might be worth doing and checking your Context path is correct in <jira_install>/conf/server.xml ( see https://confluence.atlassian.com/adminjiraserver/configuring-the-base-url-938847830.html ) (Of course in my setup I've got it behind a reverse proxy setup, so if you've got the same issue, yours might be different)

I've got the similar issue in 7.6.2 version as well

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,171 views 5 10
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