Jira 7.6.0 redirect port 80 to 443 on Centos 7

[Yevgeni]

hello all , 

I have installed jira 7.6.0 on CentOS 7 release 7.4.1708 

and did everything in this article

Jira on port 80/443 using AUTHBIND

and its still not working 

when I use nmap to see what ports are open i see only port 22

i dont know what to do anymore

any help will be much appreciated

[Yevgeni · Accepted solution]

everything works with authbind , 
apparently there is a bug that when you use config.sh
it writes the old connector 
protocol="org.apache.coyote.http11.Http11Protocol"
instead of 
protocol="org.apache.coyote.http11.Http11NioProtocol

[Nic Brough -Adaptavist-]

First question is if the service is running at all?  If it is, then what port is it exposing on the server?

[Yevgeni]

no its not working at all

the java process crashes

I have Jira 7.0.10 witch port 80 redirects to 443

when i created a test environment for the upgrade to 7.6.0

After the restore it works only on port 8080 , when I try to configure port 80 to redirect to 443 everything stops working

now i can't even make it to work on port 8443 

[Yevgeni]

everything works with authbind , 

apperently there is a bug that when you use config.sh

it writes the old connector 

protocol="org.apache.coyote.http11.Http11Protocol"

instead of 

protocol="org.apache.coyote.http11.Http11NioProtocol"

[Lars Olav Velle]

Set up an apache or nginx server in front of JIRA.

https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html

[Yevgeni]

from what i read online it messes up the gzip compression

[Nic Brough -Adaptavist-]

The volume of data being compressed is too low for gzip to matter, the offloading of work to the proxy more than makes up for it.