Slack post may have failed. Response: No hooks

[Bilalaybar]

Hi there ,

I've got multiple Jenkins and one slack team account,

I'm able to send a notification to my slack channel from 2 instances, however from my other Jenkins instance I can't.Configurations are the same.

Here are the logs that I hit Test Connection button:

Haz 02, 2017 2:48:30 PM WARNING jenkins.plugins.slack.StandardSlackService publish
Slack post may have failed. Response: No hooks
Haz 02, 2017 2:48:30 PM WARNING jenkins.plugins.slack.StandardSlackService publish
Response Code: 404

PS: Plugin versions and Jenkins Versions are same in 3 Jenkins machines.

Thank u for ur help,

[gbyukg]

The same error messages in my Jenkins server.
Jenkins version: 2.66

[ghost]

I am having the same issue. Runnins Jenkins in master/node configuration with the master as a docker container.

Has there been any progress on this at all?

Edit: I just solved this problem.

I was not using the secret storage, instead I was using the token field. Creating a credential for it as the README specifies seems to fix the issue.

[boianmihailov]

I am having the same issue, but trying to send multiple slack notifications to different organisations.
If theres settings saved in global configration, token or secret text token id, second notification always fails with error "Slack post may have failed. Response: No hooks"

[matthewlowry]

I know this is an old issue but just adding my experience:

I was getting this same error in the logs and no messages being sent, but it was a simple mistake on my part.

I had done the global configuration for the plugin, and clicked the "Test connection" button, and the test message worked as intended. But then when I ran my pipeline jobs no messages were being sent. Turned out I had simply failed to save the global configuration. In the pipeline jobs the error messages didn't say something like "Hey wait you've got no configuration", so it took me a while to work out what was going on. Oops.🥇 for me.

[alexandarp]

I started getting this error recently without making any changes to the pipeline configuration. It turns out the token was invalid and needed to be rotated. The error message wasn't very helpful.

[timja]

unfortunately we don't get much info back from slack.
Follow the steps in the README, and if you're stuck post a new issue with your problem