cannot enable slack for jira server

Edward_Apostol

As seen in the image below, we are unable to enable the slack plugin for Jira Server.

We are uncertain which logs to refer to or what type of error in the log to look for specifically. 

a recent  log entry look like this, shortly after attempting to "enable" the slack plugin

xx.yy.aa.bb 241x34164x1 username [24/Sep/2019:04:01:46 +0000] "PUT /rest/plugins/1.0/com.atlassian.jira.plugins.jira-slack-server-integration-plugin-key HTTP/1.1" 500 58 190 "https:// ... :8443/plugins/servlet/upm?source=side_nav_manage_addons" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36" "w8ksmj"

where ... is our url and xx.yy.aa.bb is the user IP

Details:

• Jira version 8.3.0 installed on Ubuntu Linux upon AWS EC2 server
• Slack for Jira Server version 2.0.1 installed with no issues.
• Only when we attempt to enable the plugin - well, it doesn't work.
• The Jira Server has https enabled. However we are serving the site through a custom port (8443) as opposed to standard 443 for SSL.
• All other plugins and server itself seems to work otherwise.

Here is the result below:

 

 

Any advice appreciated.

 

thanks

 

Edward Apostol

Luiz Silva

Hey @Edward_Apostol!

I'm sorry to hear you're having trouble with the integration. 

The information you provided is helpful but unfortunately not enough to pinpoint the cause. However, I do have some suggestions you can try:

1. Restart Jira. It's rare but sometimes the plugin system could get stuck in a dirty state and restarting it could solve the issue. If it persists though, look at the initialization logs for errors.
2. Temporarily enable debug logging.
   1. Go to System > Troubleshooting and Support > Logging & Profiling (detailed documentation) and enable DEBUG log level for the following packages:
      • <strong>com.atlassian.plugins.slack</strong>
      • <strong>com.atlassian.jira.plugins.slack</strong>
   2. Then try to enable the plugin again and now you could find more information about what happened in the logs.

Finally, if you need further assistance, please contact Atlassian support so we could have a closer look into the issue.