Jira 403 error when installing

Ross Brook March 31, 2023

Hi, I am getting a 403 when I try to setup Jira and ServiceManagement in my cluster.

This was previously working but I have taken sometime away. Now when I install the applications via helm I can reach the setup page, I edit the application name and the url click next but then fails with a 403.

Any help would be great as I am really stuck. Im not sure if it is a licence issue or not as last year we only used a temporary licence for some testing.

I tried to clean install the applications again, remove the deployments via helm and deleted then recreated the databases and then installed the application again using Helm. But still having the same issue, there are no errors in the pods running in Kubernetes as far as I can see

 

Forbidden (403)

Encountered a "403 - Forbidden" error while loading this page.

 

Go to Jira home

1 answer

0 votes
Mohit Saraf April 10, 2023

Hi, I am also getting the similar error. As soon as i click on setup page it gives 403.

 

Type Status Report

Description The server understood the request but refuses to authorize it.

 

This error is given in the logs

 http-nio-8080-exec-6 ERROR 1k5igwq [o.a.c.c.C.[.[.[/].[jsp.displayError_jsp]] Servlet.service() for servlet [jsp.displayError_jsp] threw exception
java.lang.NullPointerException
at jsp.displayError_jsp._jspService(displayError_jsp.java:121)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
... 95 filtered
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:829)
2023-04-10 22:16:12,319+0000 http-nio-8080-exec-6 ERROR 1k5igwq [o.a.c.c.C.[.[localhost].[/].[display-error-servlet]] Servlet.service() for servlet [display-error-servlet] threw exception
java.lang.NullPointerException

Corey Berkland August 31, 2023

Were either of you able to solve this issue because we are seeing the same error post-deployment?

Simon Piontek
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 13, 2023

I am having the same issue as well. Any updates? 

Corey Berkland September 13, 2023

I've reached out to my vendor contact for the data center products and they haven't been able to provide any more guidance on the Kubernetes deployments. We've been able to reach this point setting up Jira/Confluence DC within Azure, but can't move beyond it without more info because it seems like an internal issue with their installer.

Simon Piontek
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 13, 2023

Thanks for your quick replay! Good to know, I will try to figure something else out then, as we need Jira in a university setting for students and wont be able to use the cloud. 

Anyways I hope this problem will eventually be solved

Corey Berkland September 13, 2023

It looks like they can manually add a firewall rule to permit traffic if you submit your request/trace ID here: https://community.atlassian.com/t5/Jira-questions/403-ERROR-The-request-could-not-be-satisfied-Request-blocked-We/qaq-p/2431112

That said it's a pretty macgyver way of solving things, especially in the active configuration stages of setup.

Owen Chen May 7, 2024

I am having the same issue as well. Any updates? 

 

Suggest an answer

Log in or Sign up to answer