404 and 500 page error in various page in JIRA even when bypass proxy

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

404 or 500 error page when performing certain functions in JIRA, such as below:

  • moving issue
  • permission page
  • report page
  • some page cannot be rendered properly

No error in logs.

Diagnosis

Diagnostic Steps

  • 404 and 500 error page usually caused by proxy configuration
  • However, for this case, even after performing bypass proxy, issue still exist

Cause

This is either caused by a :

  • corrupted cache in JIRA
  • installation directory is running low in space

Resolution

Remove the files in the work folder, so that JIRA will be able to regenerate them when restarted. Follow below steps:

  • Stop JIRA
  • Go to $<JIRA_INSTALLATION_DIRECTORY>/work/
  • Delete the content of the work folder. DO NOT DELETE THE WORK FOLDER ITSELF

  • Check on the server.xml, ensure the connector defined is properly configured
  • Start JIRA. The file in the work folder will be recreate once JIRA is restarted
  • Retest

Ensure installation directory is given enough space.

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.