Installing Jira Service Desk on a subdomain

[FelixA]

Hello,

I try to install Jira Service Desk on a subdomain without the port 8080.

I use apache2 with SSL on an Ubuntu 18.04 server. There are more websites installed (and working) on the server. Port 443 is open and the other sites are working fine.  The subdomain is also working fine with SSL. Just Jira won't switch the port.

http://support.faltrock.com:8080 is working

But I want it on https://support.faltrock.com

I tried almost all of the tutorials and how to's found on this site here and on google but I can't figure it out.

Can someone send me a working server.xml and apache sites-available config

Thanks

[Nic Brough -Adaptavist-]

Use your Apache as a proxy server (Jira will continue to run on 8080, but Apache will pass traffic between the subdomain and your Jira on 8080) 

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

[FelixA]

That's what I am trying.

It doesn't work. 

[Nic Brough -Adaptavist-]

I am afraid "it doesn't work" tells us nothing useful.  It could be not working because there is a penguin jamming fish into the fan on the server for all we know. 

Plus, it's working fine for me.  But copying my setup might not be what you want.  You have not quite explained what you're trying to do.

What, exactly have you tried to do?  Where have you done things differently from the documentation? 

I would start by listing the files you've changed to try to make Jira listen and Apache proxy it - then look at what you've changed in each.

[FelixA]

http://support.faltrock.com:8080 is working

But I want it on https://support.faltrock.com

Of course is copy pasting what I want.

Tell me what to change and it should work.

But sending tutorials I have tried more then one time is just not helpful.

[Nic Brough -Adaptavist-]

I am sorry, I am not being clear here.

I understand you just want to be told what to do to make this happen, but we can't do that directly because:

• You have not told us what you have already changed to try to achieve the goal.  This means that we could easily tell you "change X" which would wipe out a change you have already made, or worse, compound the problems you are having, rather than improve them.
• Given your current service address is working fine, and that you want to use a (working) Apache2 to serve it on the new url, the instructions I would give you would be copied and pasted out of the documentation at the link I gave.  We are not here to copy and paste.

I'd suggest you go through the doc again and explain what you have done differently to it.