Shulou(Shulou.com)06/01 Report--

This article editor for you to introduce in detail "Jira and Confluence communication failure case analysis", the content is detailed, the steps are clear, the details are handled properly, I hope this "Jira and Confluence communication failure case analysis" article can help you solve your doubts, the following follow the editor's ideas slowly in depth, together to learn new knowledge.

Jira is a very excellent commercial project defect management tool, and Confluence is a very excellent enterprise-level WIKI. One morning, I opened the link to Confluence as usual, only to find that my login failed.

In any case, visit Jira and find that you can log in normally (here: Confluence and Jira use the same account system. Jira creates account information, and Confluence can be used directly). So I checked the application link configuration and found that the page said "remote certificate is not trusted". At that time, the first reaction was that the HTTPS free certificate expired ~ found the direction, so happily went to replace the CA certificate. Well, it turns out I can't. I went to toss about the server.xml under the conf under Confluence, but it still didn't work. I'm a little confused.

When I was desperate, I thought of the omnipotent Dafa. Reopen the Confluence container and you will find that the running container reported an error.

Visit confluence again at this time Found that the login page reported the following error (brain was buzzing at the time): com.atlassian.crowd.exception.runtime.Operationfailedexception:com.atlassian.crowd.exception.ApplicationPermissionException:Forbidden (403) occurred "403-Forbidden" error client.forbidden.exception converted to jira home page at com.atlassian.crowd.embedded.core.CrowdServicelmpl.updateUserCredential (CrowdServicelmpl.java:318) caused by:com.atlassian.crowd.exception.Applicationpermissionexception: Forbidden (403) added page "403-Forbidden' error client. Forbidden. Exception converts to Jira home page at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExectuor.thorwError (Resexecutor.java:522)

Here's a piece of advice for everyone: Docker smells good! However, it is recommended to do mirroring and data backup in advance before operation, so as to avoid unknown errors that cannot be restored. If the data is lost, it will really get cold.

According to the error prompted by iptable, look back at the IP address of the application in Jira and finally find out what the problem is. Facts have proved that if you go in the wrong direction, no matter how hard you try, it will be futile.

In the end, the Docker located to the test server was restarted by the developer's shoes, causing the ip address to be changed. Replacing the ip address in the configuration application solves the problem. But at that time, this little problem went through all day! After reading this, the article "case Analysis of Jira and Confluence Communication failure" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it yourself to understand it. If you want to know more about related articles, welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.