I would to change the configuration of my environnement.
Actually, Confluence and Jira are installed on 2 virtuals Debian servers on ESX. Jira use port 8080 and confluence 9000. Something, theses ports are blocked from outside for any reason. I would to use the SSL 443 fort both. I already use the 433 for Owncloud on another server.
Is it possible to use the port 443 for the 3 applications? Is there a procedure somewhere to do that? Thank you !
I understand you have Jira and Confluence installed to separate virtual machines and are interested in operating both of these applications using SSL over port 443. Since each application is on a separate operating system, it is technically possible that each application could use that same port number. However TCP/IP implementation across operating systems like Linux, Unix, Windows, Mac, will NOT allow more than one application on the same system to open a listening port like this at the same time.
I think the ideal way to resolve this would be to use a proxy, like Apache, nginx, etc. In a setup like this that proxy application could terminate SSL and use port 443, but then it could also be configured to route requests to the appropriate application based on either the subdomain used or the context path of the URL itself. In a setup like this it is not necessary for the native Tomcat webserver that Jira and Confluence use to actually be bound directly to using SSL on 443 on their respective virtual machines.
I would recommend checking out the guide we have in Integrating Jira with Apache using SSL. Even if you are not wanting to use Apache to implement this in your environment, it has a really good explanation of the suggested setup here. There are also additional corresponding guides for nginx as well.
Check that out and let me know if you have any follow up questions or concerns about this suggested configuration.
if i understand you, i can create another virtual server to install on it a proxy to redirect each connection to Jira, confluence or Owncloud, just by changing the sub-domain right? The proxy can rediect it? Actually, to acces to different server, it's like following :
http://xxx.synology.me:8080/jira for jira
http://xxx.synology.me:9000/confluence for confluence
https://xxx.synology.me for owncloud
I would to have the same base for each :
https://xxx.synology.me/owncloud for owncloud
https://xxx.synology.me/jira for jira
https://xxx.synology.me/confluence for confluence
Did i understand right? I can do that with a virtual proxy server on apache?
Essentially yes. I'm not familiar with owncloud, you probably can, but I'm not sure the configuration for it. Did some more searching and it looks like their site does have some documentation on using a reverse proxy much like Jira would, check out https://doc.owncloud.org/server/8.2/admin_manual/configuration_server/reverse_proxy_configuration.html for more details.
At least for Jira and Confluence server products, yes, you can certainly use Apache mod_rewrite to redirect requests based on the URL. This could be based on the subdomain such as jira123 in the example http://jira123.example.com OR you could setup a context path, such as http://jiraserver:8080/jira/ That /jira/ is a context path that you can then use with a proxy redirect to identify which client requests should be redirected to Jira.
Apache is not the only solution here, there are also other products like nginx that can do the same. The proxy server can be a virtual machine as well that runs Apache, nginx, or some other web service capable of rewriting/redirecting that web traffic.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events