Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

400 Bad Request

Paul Norrod
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!
April 22, 2026

Screenshot 2026-04-22 101444.pngScreenshot 2026-04-22 101322.png

2 answers

0 votes
Marc -Devoteam-
Community Champion
April 22, 2026

Hi @Paul Norrod 

Welcome to the community.

As your tags on the post display that this is relating a DC instance, look at the log files on the server Jira is running on.

If oyu can't contact your Jira admin or the local IT department to help out.

0 votes
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 22, 2026

Hi and welcome to the Community @Paul Norrod 

The "400 Bad Request Request Header Or Cookie Too Large" message from nginx is the key detail here. It usually means that either Jira or the reverse proxy sitting in front of it is hitting a limit on the size of the headers or cookies your browser is sending. Since GitHub is a perfectly valid host for the plugin, the problem is likely with the request size rather than your Git configuration.

I’d suggest testing this in an incognito window first to see if that clears it up. If it works, you’re probably dealing with "cookie bloat" from your SSO or a browser extension that's stuffing too much data into your headers. If it still fails, your Jira admin will likely need to adjust the "maxHttpHeaderSize"  in the Tomcat or Nginx settings. It looks like Jigit is just passing along a low-level infrastructure error, so focusing on those server limits is your best bet.

Ramsudhakar Vedula
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!
April 22, 2026

jira.conf  (Apache)

<VirtualHost *:443>
ServerName m
Include /etc/httpd/ssl/ddd.dd.include
LimitRequestFieldSize 65536
LimitRequestLine 65536
LimitRequestFields 200
UseCanonicalName Off
ServerAdmin webmaster@localhost
ProxyRequests Off
ProxyPreserveHost On
ProxyTimeout 300
AllowEncodedSlashes NoDecode

# Dont proxy the loadbalancer alive request
ProxyPass /default.aspx !

<Proxy *>
Order deny,allow
Allow from all
</Proxy>
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"

# To disable access and show maintenance message comment next 2 lines
ProxyPass / http://localhost:8080/ nocanon
ProxyPassReverse / http://localhost:8080/
</VirtualHost>

 

 

on the tomcat server.xml

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
connectionTimeout="20000" redirectPort="8443"
maxThreads="150" minSpareThreads="25" disableUploadTimeout="true" bindOnInit="false"
enableLookups="false" acceptCount="100" URIEncoding="UTF-8" maxHttpHeaderSize="65536"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="jira.oii.oceaneering.com" proxyPort="443">
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
</Connector>

 

 

Above are our current settings. Any suggested values?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
10.3.4
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events