Hi All,
Need quick help please.
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: DNS lookup failure for: jira.dev.<company.edu>
Apache/2.2.15 (Red Hat) Server at jira.dev.<company.edu> Port 443
Thanks,
Navadeep
Thanks for quick response Josh.
Checked the /etc/hosts file
It looks fine.
The error also shows below
Apache/2.2.15 (Red Hat) Server at jira.dev.<company.edu> Port 443
What exactly do I need to check in the proxy configuration file in apache
Thanks,
I assume it's /etc/httpd/conf.d/ssl.conf
If you followed the documentation, there should be some parts you added to handle the proxy, such as ProxyPass and ProxyPassReverse directives. Also you should have modified the standard /jirainstalldir/conf/server.xml
Did you use this documentation page? https://confluence.atlassian.com/adminjiraserver073/integrating-jira-with-apache-using-ssl-861253896.html
I checked the ssl.conf.
SSLProxyEngine On
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / http://jira.dev.<company.edu>8080/
ProxyPassReverse / http://jira.dev.company.edu:8080/
It is showing as above.
in Server.xml what things I need to check clearly..
Thanks,
You'll need to have a connector object in server.xml like this:
<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" scheme="https" proxyName="jira.dev.company.edu" proxyPort="443" secure="true"/>
<Connector port="8080"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"
proxyName="jira.dev.company.edu"
scheme="https"
proxyPort="443"
secure="true"/>
Above is the content how it is defined in the file.. It also looks fine I guess..
Any other reasons why I am not able to access still ? Or restart JIRA will help out anyway ?
If you haven't restarted JIRA since modifying the server.xml, you need to do that.