Jira镜像容器化后nginx反向代理的配置

最新推荐文章于 2022-12-27 17:39:34 发布

Blue_Tear

最新推荐文章于 2022-12-27 17:39:34 发布

阅读量2.2k

点赞数 3

分类专栏：项目管理 docker jira k8s

本文链接：https://blog.csdn.net/Blue_Tear/article/details/83662418

版权

本文介绍了在Docker容器化Jira时遇到的nginx反向代理配置问题。官方和常见教程建议修改<JIRA-INSTALL>/conf/server.xml，但在容器化的Jira中，需要注意镜像内存在3个8080端口配置。作者发现直接修改可能不会生效，并分享了解决方案：注释掉第一个端口配置，启用第二个端口。此外，由于配置文件位于非挂载目录，重启容器会导致配置丢失。通过设置环境变量在启动容器前修改server.xml，可以解决配置持久化问题。然而，文章指出在k8s环境中多副本Jira仍存在冲突问题，以及Jira与MySQL5.6以上版本的连接协议问题。

摘要由CSDN通过智能技术生成

问题描述：

如果docker容器化jira，使用官方的镜像cptactionhank/atlassian-jira-software:latest,通常会配置域名（ex:jira.test.com)进行访问，如使用nginx进行反向代理。会出现以下错误：

com.atlassian.gadgets.dashboard.internal.diagnostics.UrlHostnameMismatchException: Detected URL hostname, '192.168.10.165', does not match expected hostname, 'jira.proxy.com'

We’ve detected a potential problem with JIRA’s Dashboard configuration that your administrator can correct. Hide 
Dashboard Diagnostics: Mismatched URL Scheme 
JIRA is reporting that it is using the URL scheme ‘http’, which does not match the scheme used to run these diagnostics, ‘https’. This is known to cause JIRA to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues. 
The most common cause of this is the use of a reverse-proxy HTTP(S) server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct scheme.
The following articles describe the issue and the steps you should take to ensure that your web server and app server are c