-
Suggestion
-
Resolution: Fixed
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
In JIRA 7.1 when accessing the Dashboard, JIRA gadgets use themselves as proxy, with the fully resolvable host name - so the JIRA instance needs to be able to access itself. If it's not able to do so (for example basic auth on a proxy layer, the domain name is not resolvable, it's served on an IP that's in a separate restricted subnet to the server JIRA is running on or JIRA is served with a self-signed certificate that doesn't exist in its own trust store) this error will occur.
Suggested Solution
Implement healthcheck in JIRA which will connect to BaseURL, mimicking call which will be done for gadgets. This will help in troubleshooting the problem.
Workaround
Use curl command from JIRA server:
curl -v '<JIRA_URL>'
Notes
See How to fix gadget titles showing as __MSG_gadget and JRA-59892 for details
- is related to
-
JRASERVER-59892 Gadgets title are showing as __MSG_gadget.xxxxxxx
-
- Closed
-
-
JSEV-141 You do not have permission to view this issue
- relates to
-
JRASERVER-60572 Document JIRA's requirement to be able to communicate with itself with it's base URL
-
- Closed
-
As an Administrator I want check if JIRA is able to connect to BaseURL
-
Suggestion
-
Resolution: Fixed
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
In JIRA 7.1 when accessing the Dashboard, JIRA gadgets use themselves as proxy, with the fully resolvable host name - so the JIRA instance needs to be able to access itself. If it's not able to do so (for example basic auth on a proxy layer, the domain name is not resolvable, it's served on an IP that's in a separate restricted subnet to the server JIRA is running on or JIRA is served with a self-signed certificate that doesn't exist in its own trust store) this error will occur.
Suggested Solution
Implement healthcheck in JIRA which will connect to BaseURL, mimicking call which will be done for gadgets. This will help in troubleshooting the problem.
Workaround
Use curl command from JIRA server:
curl -v '<JIRA_URL>'
Notes
See How to fix gadget titles showing as __MSG_gadget and JRA-59892 for details
- is related to
-
JRASERVER-59892 Gadgets title are showing as __MSG_gadget.xxxxxxx
-
- Closed
-
-
JSEV-141 Loading...
- relates to
-
JRASERVER-60572 Document JIRA's requirement to be able to communicate with itself with it's base URL
-
- Closed
-