All my gadgets have bad titles. Jira is running behind http proxy
I receive this message when I when login "
Also, the Instant Health check shows the error below.
Thanks Brant for your response. I followed the steps to add the Jira server's hostname to the proxy configuration and ran curl command to connect to the jira server. It connects but I got ssl error as shown below. The certificate has not expired and the domain is correct.
* start date: Nov 25 00:00:00 2020 GMT
* expire date: Oct 02 23:59:59 2021 GMT
* common name: *.xxx.xx
* issuer: CN=DigiCert TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US
* NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER)
* Peer's Certificate issuer is not recognized.
* Closing connection 0
curl: (60) Peer's Certificate issuer is not recognized.
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Can someone from Jira Support call me on the phone to help me troubleshoot the issue?
So your team asks client to modify their routing table in order a web application could run...
Why don't you make a call at application level ?? (increase response time by a factor of 100 !!)
Why don't you have an "internal" URL in jira ??
These workarounds are security holes... and most important : PAIN for customers !
In a world of automatic deployments this is not possible anymore to customize system like this just to hide a bad functionnality... !
I hope your team really reconsider remove this 'local call"....