JIRA throws 'Page Not Found'

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Symptoms

  1. JIRA has been restarted

  2. JIRA throws blank page with Error 'Page Not Found'

The following appears in the JIRA log :

1 2 3 4 5 Jun 13, 2012 2:33:14 AM org.apache.coyote.http11.Http11AprProtocol init SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [730013] An attempt was made to access a socket in a way forbidden by its access permissions. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:649) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107)

Cause

There is other application using the same port that is used by JIRA.

Resolution

  1. Ensure that the port number JIRA listening to is available

  2. Restart JIRA instance

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.