Accessing https Jira via port 443

[Rahul Aich [Nagra]]

Guys

let me re-phrase my issue i posted last night.

Last night I tried to access jira using default ports i.e. 80 and 443 (by amending the server.xml port numbers) then accessing it through http://localhost:80 and https:localhost:443. But I received apache 404 error page. However, if i used any other random port it worked yesterday.

Today morning i uninstalled jira and did afresh installation and it worked. jira could then be accessed through all ports inc 80 and 443.

This now confirms that it was nothing to do with firewalls.

Any idea what may have been the root cause of the issue?

PS: I have a standalone installation on windows server.

Rahul

[Jason Hensler · Accepted solution]

I would take a look at either this guide https://confluence.atlassian.com/display/JIRA052/Integrating+JIRA+with+Apache+using+SSL or

this guide https://confluence.atlassian.com/display/JIRA052/Running+JIRA+over+SSL+or+HTTPS.

When you say apache 404 page do you mean the apache tomcat or are you running an apache httpd in front of jira? If you are running httpd, then you need to add your mod_proxy or mod_jk setting to the ssl vhost config in the httpd-ssl.conf file.

[Rahul Aich [Nagra]]

Jason

yes i meant 404 page apache tomcat.....it is a standalone installation...if i use 8443 it works but not with 443....

[Jason Hensler]

can you post your server.xml file so we can see what might be the issue.

[Rahul Aich [Nagra]]

Hi Jason

It seems i have managed to resolve it. I uninstalled the jira and performed a fresh installation, patched the old server.xml. It then started accepting the default ports i.e. 80 and 443.

i.e. http://localhost and https://localhost started working.

But I am still unclear on why the webserver did not respond to 80 and 443 yesterday although it was responding to all other random ports. Any idea>

Rahul

[Jason Hensler]

I think that the defaut connector config in the server.xml was taking over.

<Connector port="8080" disableUploadTimeout="true" acceptCount="100" redirectPort="8443" useBodyEncodingForURI="true" protocol="HTTP/1.1"
 maxHttpHeaderSize="8192" enableLookups="false" connectionTimeout="20000" minSpareThreads="25" maxThreads="150"/>

You said it was working on port 8443 which is defined in the default connector as redirectPort. The Tomcat manual says this about the redirectPort:

"If this Connector is supporting non-SSL requests, and a request is received for which a matching <security-constraint> requires SSL transport, Catalina will automatically redirect the request to the port number specified here." link

It would seem that tomcat was picking up 8443 as the ssl port, not 443. I would guess that you could change the redirectPort to 443, configure the ssl options, and it would work. 8443 is the defualt value from the Tomcat project because, ports under 1024 on unix must be run under a root user.

[Rahul Aich [Nagra]]

When I uninstalled the Jira and re-installed it started accepting the port 443. I am still not sure what caused the problem. But anyways, thanks everyone for your responses earlier.

Rahul

[B_ Normann P_ Nielsen]

Also, I think that post in the low range below 1024 are restricted, hence You need to run jira as root (not as jira) to use them, see this old link:

http://www.staldal.nu/tech/2007/10/31/why-can-only-root-listen-to-ports-below-1024/

[Kelly Schoenhofen]

But he said he was running this on Windows, which doesn't have the sub-1024 block in place.

[Ramiro Pointis]

Hi Rahul, please make sure that you have configured proxy settings (if you are behind one). And check too if some other service is using the same port.

[Ramiro Pointis]

Check this page too, could be another option:

http://www.xaviermorera.com/2011/09/jira-404-error-the-requested-resource-is-not-available-apache-tomcat6-0-32/

[Rahul Aich [Nagra]]

is server.xml the only place to change if i have to change the ports?

Rahul

[Ramiro Pointis]

You can use the Jira Configuration Tool too but I think it's the same thing (much cleaner). Check it here:

https://confluence.atlassian.com/display/JIRA/Using+the+JIRA+Configuration+Tool