Hi guys,
I don´t know how to proceed with our jira Service desk Project.
Please excuse my mistakes, I am German and my Keyboard forces its german layout. whatever :-D
The following Scenario works Wonderful with http but doesn´t do it with ssl.
I have Jira installed in a virtual machine running on a Hypervisor with VMware installed.
I am using the Standard port for http. The OS jira is running on is Debian 9.5 Linux.
It drives me mad trying to establish a secure Connection over ssl.
I can reach the machine via the internal IP - perfect. So far so good. But when I Import my Wildcard Certificate for the public IP and Domain of the Company I do not get it to work properly.
We are using a Sophos UTM 9.6 where all the traffic has to pass through. I tried Setting up Proxy over apache2 or nginx in the Linux machine - without success. I tried to Setup a WAF via Sophos - without success.
Is there any Chance to get this done?
Our customers have to reach the System over https otherwise data security isn´t given anymore and in times of the General Data Protection Regulation this is pure Horror.
I would be pleased if anyone could help me here.
Thanks guys in Advance.
Chris
@Christof Lemke Did you follow this Atlassian guide for configuring nginx reverse proxy for JIRA?
https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html
I tried a bunch of Guidelines, with Apache or nginx, with or without Proxy but Nothing works. It´s a disaster. The Software Costs almost 5000 Dollars.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Christof Lemke If you have a commercial license for your Atlassian product and you are facing a specific issue that you think cannot be resolved on your own, it is not a known issue with Atlassian or no similar post exists in Atlassian Community to provide you any guidance, I would suggest to please contact Atlassian Support (https://support.atlassian.com/) , providing all specific details of the issue (including logs).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To resolve this SSL issue with Jira Service Desk, simply add the following environment variables to your container:
- ATL_PROXY_NAME=example.com
- ATL_TOMCAT_SECURE=true
- ATL_PROXY_PORT=443
- ATL_TOMCAT_SCHEME=https
You can follow this: https://hub.docker.com/r/atlassian/jira-software
Using this method to update the configuration files is simpler than constructing a separate volume for server.xml file, I hope this helps. Positive vibes and best wishes for your project. 👍
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.