nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira ports redirecting

Vitaliy_0frsun

Hi all!
I have some issue about port redirecting with our jira. Wen yuo going to http://jira.mydomain.com it will redirect you to https://jira.mydomain.com and its nice. But if you will go to jira.mydomain.com:8080 you will get connection over 8080 port without redirecting to https. I am new in atlassian product so I ask for advice.
Our Vhosts:

VirtualHost *:443>
ServerName jira.mydomain.com
ProxyRequests Off
ProxyPreserveHost Off
ProxyPass / http://127.0.0.1:8080/
ProxyPassReverse / http://127.0.0.1:8080/
RemoteIPHeader X-Forwarded-For
SSLEngine On
SSLCertificateFile /data/ssl/jira.mydomain.com--2017.09.15--crt.txt
SSLCertificateKeyFile /data/ssl/jira.mydomain.com--2017.09.15--key.txt
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
</VirtualHost>

<VirtualHost *:80>
ServerName jira.mydomain.com
Redirect Permanent / https://jira.mydomain.com/
RemoteIPHeader X-Forwarded-For
</VirtualHost>

Here is server.xml I suppose problem is here

<Service name="Catalina">

<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"
bindOnInit="false"

scheme="https"
proxyName="jira.mydomain.com"
proxyPort="443"
secure="false"
/>

Accepted answers

Gonchik Tsymzhitov

Hi!

For history I changed added again my comment with right answer.

I have tried on VM this command for external interface.

sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 8080 -j REDIRECT --to-port 80

Cheers,

Gonchik Tsymzhitov

All comments

Nic Brough -Adaptavist-

Try copying the "Virtualhost *:80" to a second one. Same content, but "Virtualhost *:8080"

Gonchik Tsymzhitov

Hi!

As I understand you are provide very good idea.

if you have issue about port conflicting. Hence you need to set for localhost tomcat connector

<Service name="Catalina">

<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"
bindOnInit="false"

 address="127.0.0.1"

scheme="https"
proxyName="jira.mydomain.com"
proxyPort="443"
secure="false"
/>

and for external ip address for apache2

<VirtualHost EXTERNAL_IP:8080>
ServerName jira.mydomain.com
Redirect Permanent / https://jira.mydomain.com/
RemoteIPHeader X-Forwarded-For
</VirtualHost>

Hence It will works.

Cheers,

Gonchik Tsymzhitov

Vitaliy_0frsun

Thanks for your help!

But ... it didn't help me (

If I in server.xml set address="127.0.0.1"

http://jira.mydomain.com:8080 telling me that "This site can’t be reached"

And without address only with added Virtualhost 8080

http://jira.mydomain.com:8080 still not redirect me to https, and i don`t understand why

Nic Brough -Adaptavist-

Try removing the address line from your server.xml, you don't need it.

Gonchik Tsymzhitov

Hi!

For history I changed added again my comment with right answer.

I have tried on VM this command for external interface.

sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 8080 -j REDIRECT --to-port 80

Cheers,

Gonchik Tsymzhitov

Suresh_b3sg6g

Hi Gonchik,
We too have same issue, but the above command need to run every time after sever restart to take effect.
Do we have any permanent solution?

Regards,

Nic Brough -Adaptavist-

The standard way to do it is with the commands iptables-save and iptables-restore in the shutdown and startup scripts for the machine, but the package iptables-persistent is a nice wrapper that saves you having to do most of the config for them.

Suresh_b3sg6g

Thank you, Nic.

Is there any alternate solution to redirect to https for the above, instead of changing itables.