nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot View Custom Fields and Project Fields pages

Doods Perea_6ykzuy

Our JIRA Administrators are unable to view either the Custom Fields page or the Fields page of any project. The browser shows the following error:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /plugins/servlet/project-config/PCWORKS/fields.

Reason: Error reading from remote server

Prior to this error, we migrated the application to our Data Center and then I did a background re-index that took almost a week to complete. I suspect that because background re-index allows users to work in JIRA, changes to the configuration, new/modified custom fields, among others may have caused for the error to occur.

Accepted answers

Doods Perea_6ykzuy

With the migration to our Data Center, the dbconfig.xml file had to be updated to point to the new database server.

All comments

Moses Thomas_08kyb0

@Doods PereaPlease which proxy server are you using ? (apache or ngnix) ?

Doods Perea_6ykzuy

Thanks @Moses Thomas - we are using Apache Proxy Server.

Moses Thomas_08kyb0

@Doods PereaI suspect you have the same issue please follow solution here.

https://community.atlassian.com/t5/Jira-questions/Users-receive-proxy-error-when-trying-to-login-to-confluence/qaq-p/805609#M259763

Best!

Doods Perea_6ykzuy

Thanks @Moses Thomas - what sort of error am I supposed to see in the log file(s), and which log file(s) am I supposed to check?

In the atlassian-jira.log file, I saw this error when accessing the Fields page of project PCWORKS:

2018-06-04 04:30:22,306 http-nio-8088-exec-57 ERROR DINDO922 262x377463x2 1ktwghu 10.230.28.135,10.165.233.27 /plugins/servlet/project-config/PCWORKS/fields [c.a.p.webresource.assembler.DefaultWebResourceAssembler] Error generating bigpipe content for 'sidebar-id': Deadline exceeded
java.lang.RuntimeException: Deadline exceeded
at com.atlassian.plugin.webresource.bigpipe.QueueFutureCompletionService.forceCompleteAll(QueueFutureCompletionService.java:62)
at com.atlassian.plugin.webresource.bigpipe.BigPipe.forceCompleteAll(BigPipe.java:33)

......

Googling "Error generating bigpipe content for 'sidebar-id': Deadline exceeded", one result it returned is Atlassian JIRA ticket https://jira.atlassian.com/browse/JRASERVER-64095.

Do you think this error we are experiencing is related to "BIGPIPE"? I should re-state that this is the only page that causes the error. We (JIRA Admins) are able to see the other configuration pages of the project.

Thanks,

Doods

Doods Perea_6ykzuy

I tried each of the following but the error remains when I tried open the Custom Fields or the Project Fields page.

Rebuilt the JIRA index.
Entered in Safe Mode.
Enabled the dark feature “atlassian.jira.config.BIG_PIPE_KILLSWITCH” as recommended in https://jira.atlassian.com/browse/JRASERVER-64095.
Stopped JIRA service. Removed all add-ons. Started JIRA Service.

Any thoughts on why this error occurs? Could it really be the Apache Reverse Proxy setting that is the culprit? Why is it that only the Custom Fields and Project Fields are affected? Why are the other pages displaying normally?

Thanks,

Doods

Moses Thomas_08kyb0

@Doods PereaI suggest you first check what happens without reverse proxy if every thing should go well then you need to make sure that your Apache reverse proxy server setting is not faulty as this was the problem you first encountered, then you might get rid of this issue.

Best!

Doods Perea_6ykzuy

Thanks again for your help @Moses Thomas.

Upon further review, we found out that the cause for this error was that the dbconfig.xml is configured to point to the old database in the old server.

We corrected this file and now JIRA-UAT is functioning as expected.

Best!

Doods

Doods Perea_6ykzuy

With the migration to our Data Center, the dbconfig.xml file had to be updated to point to the new database server.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-core