Slack publish failed, response code 404 #480

amit-o · 2019-01-17T09:44:56Z

I'm trying to setup slack integration on a docker running in localhost.
When trying to publish or test connection in the settings, I'm getting this in the logs:

Jan 17, 2019 9:37:55 AM jenkins.plugins.slack.StandardSlackService publish
WARNING: Slack post may have failed. Response: null
Jan 17, 2019 9:37:55 AM jenkins.plugins.slack.StandardSlackService publish
WARNING: Response Code: 404

The same configurations are working in a non-docker configurations


    slackNotifier:
      tokenCredentialId: slack-token
      teamDomain: <workspace>
      baseUrl: https://<workspace>.slack.com/services/hooks/jenkins-ci/  
 credentials:
    system:
      domainCredentials:
            - string:
                scope: GLOBAL
                id: slack-token
                secret: ${SLACK_TOKEN}

The text was updated successfully, but these errors were encountered:

timja · 2019-01-17T10:10:21Z

Hi don't set teamDomain and baseUrl

only set teamDomain, may or may not be your issue.

But docker vs non docker probably isn't the issue

amit-o · 2019-01-17T11:00:41Z

I've tried setting teamDomain only and baseUrl only, still the same issue

timja · 2019-01-17T11:05:12Z

is the slack token correct?

amit-o · 2019-01-17T11:15:05Z

Yes, I've posted manually with curl and token and the message was sent successfully

timja · 2019-01-17T11:15:49Z

is it correct in jenkins though?
if you add a credential manually in the ui and select that one does it work?

amit-o · 2019-01-17T11:25:53Z

Tried putting it in through the UI and deselected the credentialId, same error.

timja · 2019-01-17T11:26:55Z

what about with a separate credential?

amit-o · 2019-01-17T11:33:54Z

Do you mean a different slack token?
If so, just tried it and still no dice

gregbishop · 2019-01-17T20:29:10Z

I actually get this issue as well. What is particularly weird about it is that it only seems to fail when I send a message to certain users. It seems to be only newer users at the company (age of slack account may be a red herring, but I don't know). At this point I have no idea what else to do.

Jalle19 · 2019-01-23T12:35:44Z

Seeing this problem as well, it started happening quite recently (less than a week ago)

Jalle19 · 2019-01-23T12:58:18Z

WTF, in our case the problem was that someone (or Slack themselves?) had disabled the Jenkins CI app from Slack's integration settings. Clicked "enable" and it started working.

timja · 2019-01-23T13:17:20Z

@Jalle19 That could happen if the person who previously added it had their slack account disabled

esproul · 2019-02-06T14:46:09Z

I am having the same issue. I am unable to successfully "Test Connection". I have an "Outgoing Webhook Token" and "Outgoing Webhook URL Endpoint" set under "Slack Webhook Settings" (I get warnings if I leave either one blank). Further down, under "Global Slack Notifier Settings" I have:

Slack compatible app URL: (blank)
Team subdomain: (set to our Slack subdomain)
Integration Token Credential ID: set as Secret Text type per README.md#security
Is Bot User? is unchecked
Channel or Slack ID: set to our desired channel

When I try to test the connection, I see in the server log:

Feb 06, 2019 2:44:44 PM jenkins.plugins.slack.StandardSlackService publish
WARNING: Slack post may have failed. Response: null
Feb 06, 2019 2:44:44 PM jenkins.plugins.slack.StandardSlackService publish
WARNING: Response Code: 404

Jenkins 2.163, Slack plugin 2.15

timja · 2019-02-06T14:47:20Z

Is the slack app integrated into at least one channel?

esproul · 2019-02-06T14:51:28Z

Yes, I have one active configuration, into the same channel configured in the global notifier settings in Jenkins.

timja · 2019-02-06T14:53:14Z

check your team domain is just the team name and not the full name
try regenerate the token

not really sure sorry, just check it's all been setup right

esproul · 2019-02-06T14:57:52Z

Team subdomain is just the subdomain, no ".slack.com". I regenerated the token and updated it in Jenkins, but no change, still 404.

esproul · 2019-02-06T16:55:45Z

Downgrading Slack notification plugin to 2.6 (the last working version I've been trying to upgrade from), I now see:

Feb 06, 2019 4:52:29 PM jenkins.plugins.slack.StandardSlackService publish
WARNING: Slack post may have failed. Response: no_active_hooks
Feb 06, 2019 4:52:29 PM jenkins.plugins.slack.StandardSlackService publish
WARNING: Response Code: 404

If I restore my integration token to the global config, it works.

timja · 2019-02-06T16:57:46Z

interesting, i can't see anything around there that should have broken it
so on 2.6 with a credential it works properly and on 2.15 its broken?

esproul · 2019-02-06T17:06:59Z

On 2.6 with an integration token (no credential ID) it works. On 2.15, regardless of any settings (with/without token, with/without credential ID), it doesn't work for me.

saamorim · 2019-02-06T19:14:13Z

For me, with the version 2.15 I if I use the tokenCredentialId I have the 404 reported before. The work around for me was to use the withCredentials.

Non working version:

slackSend teamDomain: 'domain', channel: 'pipeline-cicd', tokenCredentialId: 'slackCredentials',  color: 'danger', message: 'Not so good message from Jenkins Pipeline'

Working version:

withCredentials([string(credentialsId: 'slack-credentials', variable: 'slackCredentials')]) {
    slackSend teamDomain: 'domain',
        channel: 'pipeline-cicd', 
        token: slackCredentials, 
        color: 'danger',
        message: 'Not so good message from Jenkins Pipeline'
}

timja · 2019-02-06T19:51:40Z

I'm wondering if there's some encoding issue in the secret

Would need to log the request to see what the token is,
You can either try setting a log recorder for org.apache.http.wire FINE
Or i'll have a debug build ready shortly

timja · 2019-02-06T19:53:53Z

If you change jenkins.plugins.slack.StandardSlackService to fine it will be logged
can you compare both versions please

"Posting: to " + roomId + " on " + teamDomain + " using " + url + ": " + attachments.toString() + " " + color
It'll be in the URL

gmsa · 2019-02-07T13:14:14Z

I had the same problem and managed to get it working.
You need to set the integration token as a jenkins credential ID. The integration token input field is there, but seems to be ignored by the plugin.

esproul · 2019-02-07T13:47:44Z

@gmsa do you mean setting the integration token as the "secret text" of the jenkins credential?

gmsa · 2019-02-07T13:48:29Z

@esproul yes

esproul · 2019-02-07T14:06:14Z

Cool, 2.15 now works, and I didn't have to do anything; after this most recent upgrade I have a "Migrated Slack Token" credential ID. "Test Connection" succeeds. I don't know if this made a difference, but yesterday after downgrading back to 2.6, I noticed a number of jobs that had the integration token in their job config, when it didn't need to be (none of my jobs need to override the global settings.) I went through and cleaned those out; not sure if that would have interfered with the automatic migration of the global token or not.

esproul · 2019-02-07T14:07:13Z

@timja @gmsa thank you for your help!

tiendungitd · 2019-05-28T07:51:11Z

I got the same issue with version 2.22, integration token as a jenkins credential ID is work for me. But could this issue fix in new version?
Seen like the version 2.14 work well without the workaround above?

timja · 2019-05-28T08:02:09Z

what specifically was your issue @tiendungitd? there's many things that can go wrong and cause that issue

tiendungitd · 2019-05-28T08:33:40Z

@timja : In build job configuration, the "integratoin token" field have been ingore. under "Slack Notifications" I have:

- Slack compatible app URL: https://{workspace}.slack.com/services/hooks/jenkins-ci/
- Team subdomain: (blank)
- Integration Token: cu6lsj1t9Eh81119Q8kyT0f
- Integration Token Credential ID: none
- Is Bot User? is unchecked
- Channel or Slack ID: #general

I got failed when click test connection, look at system log I found the error:
Slack post may have failed. Response: no_active_hooks, then I using "Integration Token Credential ID" fix the issue, but I expect using "Integration Token" field

And if I setting Slack notification is:

- Slack compatible app URL: (blank)
- Team subdomain: my-workspace
- Integration Token: cu6lsj1t9Eh81119Q8kyT0f
- Integration Token Credential ID: none

I got success when click Test connection, event I type incorrect token and of course my job build not send anything to slack.

I'm using Jenkins 2.164.2. Slack plugin version 2.22.

JamesMahy · 2019-05-30T14:34:41Z

Hi,

I'm running 2.23.
There is no "Integration Token" field (as per the instructions shown on slack)

I've installed the Slack Integration and also tried with a bot using an incoming hook. Neither work.

If I use

Slack compatible app URL (optional) = empty
Subdomain = myslackservername,
Integration Token Credential ID = Client Token, Secret
Is Bot User = Checked,
Channel = #notifications

I get

[JobName #35] will send OnSuccessNotification because build matches and user preferences allow it
and no error but nothing in the slack channel

If I use

Slack compatible app URL (optional) = https://hooks.slack.com/services/[LONG_TOKEN]
Subdomain = myslackservername,
Integration Token Credential ID = Client Token, Secret
Is Bot User = Checked,
Channel = #notifications

I get

[JobName #36] will send OnSuccessNotification because build matches and user preferences allow it May 30, 2019 3:25:56 PM WARNING jenkins.plugins.slack.StandardSlackService publish Slack post may have failed. Response: May 30, 2019 3:25:56 PM WARNING jenkins.plugins.slack.StandardSlackService publish Response Code: 302

If I use

Slack compatible app URL (optional) = https://hooks.slack.com/services/[LONG_TOKEN]
Subdomain = empty,
Integration Token Credential ID = -none-
Is Bot User = Checked,
Channel = #notifications

I get
[JobName #37] will send OnSuccessNotification because build matches and user preferences allow it May 30, 2019 3:28:20 PM INFO jenkins.plugins.slack.logging.SlackNotificationsLogger info [JobName #37] Exception attempting Slack notification: the token with the provided ID could not be found and no token was specified

If I use

Slack compatible app URL (optional) = https://hooks.slack.com/services/[LONG_TOKEN]
Subdomain = empty,
Integration Token Credential ID = Client Token, Secret
Is Bot User = Checked,
Channel = #notifications

I get
[JobName #38] will send OnSuccessNotification because build matches and user preferences allow it May 30, 2019 3:30:13 PM WARNING jenkins.plugins.slack.StandardSlackService publish Slack post may have failed. Response: May 30, 2019 3:30:13 PM WARNING jenkins.plugins.slack.StandardSlackService publish Response Code: 302

There aren't any combinations in which this works - but I can manually call the hook using curl.
Also the documentation is out of date or there is a missing Integration token field (assuming out of date as "Slack compatible app URL (optional)" says "Base URL" in the documentation.

timja · 2019-05-30T14:35:46Z

you probably want bot user false

JamesMahy · 2019-05-30T14:37:56Z

Checked or unchecked it doesn't solve the problem in any scenario. I get "302" and no response.

timja · 2019-05-30T14:39:18Z

can you screenshot please?

JamesMahy · 2019-05-30T14:40:34Z

I get 302 if I hit "Test"
I get 404 if I try following a build.

JamesMahy · 2019-05-30T14:47:22Z

These are the instructions on Slack, which are no longer viable.

timja · 2019-05-30T15:28:44Z

No the slack instructions are wrong, I asked them to update it but it didn't happen...

Team subdomain
Credential ID
channel

The instructions on the README should be up to date

JamesMahy · 2019-05-30T16:35:03Z

Unfortunately it doesn't work with any settings.

xorgnz · 2019-06-26T19:02:50Z

I'm having a similar issue. Is there anything I can do to get it to spit out more log info so that I can try and make sense of this? Or should I break out the network analyzer to see what's going back and forth?

Running "test connection" in the admin just lists "Failure" in red. In the logs I see the same 404 issue described here. I'm running version 2.27 of the plugin

timja · 2019-06-26T19:37:30Z

@xorgnz you can add a log recorder to this class:
jenkins.plugins.slack.StandardSlackService
also see:
#480 (comment)

xorgnz · 2019-06-27T04:13:43Z

Thanks! That was very helpful. I appear to be working (seems the plugin hadn't installed properly)

ckime-ibm · 2020-08-23T22:31:50Z

The withCredentials solution did not work for me, in a Jenkins pipeline job.

The "global"/default credentials specified in the Slack plug-in configuration did not seem to work. I created a new global credentials, and specified with tokenCrendentialId and finally had a successful slackSend.

My git diff in case it helps anyone:

                     slackSend channel: "#slack-channel-name",
-                                message: "Build message - SUCCESS",
-                                color: "good",
-                                baseUrl: "https://my-domain.slack.com/services/hooks/jenkins-ci/",
-                                token: "${SLACK_CHANNEL_TOKEN}"
+                        teamDomain: "my-domain",
+                        message: "Build message with tokenCredentialID - SUCCESS",
+                        color: "good",
+                        // Do not specify baseURL w/Channel.  
+                        //baseUrl: "https://ibm-ai-apps.slack.com/services/hooks/jenkins-ci/",
+                        // 404 with token, works with this tokenCredentialId.
+                        //token: "${SLACK_CHANNEL_TOKEN}"
+                        tokenCredentialId: "ai-apps-slack-token"

timja mentioned this issue Feb 6, 2019

2.15 release - migrate Integration token into a credential but credential fails #507

Closed

timja closed this as completed Mar 18, 2019

gremito mentioned this issue Dec 19, 2019

Response: null, Response Code: 404 and Response: {"ok":false,"error":"invalid_auth"} #649

Closed

Slack publish failed, response code 404 #480

Slack publish failed, response code 404 #480

Comments

amit-o commented Jan 17, 2019

timja commented Jan 17, 2019

amit-o commented Jan 17, 2019

timja commented Jan 17, 2019

amit-o commented Jan 17, 2019

timja commented Jan 17, 2019

amit-o commented Jan 17, 2019

timja commented Jan 17, 2019

amit-o commented Jan 17, 2019

gregbishop commented Jan 17, 2019

Jalle19 commented Jan 23, 2019

Jalle19 commented Jan 23, 2019

timja commented Jan 23, 2019

esproul commented Feb 6, 2019

timja commented Feb 6, 2019

esproul commented Feb 6, 2019

timja commented Feb 6, 2019

esproul commented Feb 6, 2019

esproul commented Feb 6, 2019

timja commented Feb 6, 2019

esproul commented Feb 6, 2019

saamorim commented Feb 6, 2019 • edited Loading

timja commented Feb 6, 2019

timja commented Feb 6, 2019 • edited Loading

gmsa commented Feb 7, 2019

esproul commented Feb 7, 2019

gmsa commented Feb 7, 2019

esproul commented Feb 7, 2019

esproul commented Feb 7, 2019

tiendungitd commented May 28, 2019

timja commented May 28, 2019

tiendungitd commented May 28, 2019

JamesMahy commented May 30, 2019 • edited Loading

timja commented May 30, 2019

JamesMahy commented May 30, 2019

timja commented May 30, 2019

JamesMahy commented May 30, 2019

JamesMahy commented May 30, 2019

timja commented May 30, 2019

JamesMahy commented May 30, 2019

xorgnz commented Jun 26, 2019

timja commented Jun 26, 2019

xorgnz commented Jun 27, 2019 • edited Loading

ckime-ibm commented Aug 23, 2020

saamorim commented Feb 6, 2019 •

edited

Loading

timja commented Feb 6, 2019 •

edited

Loading

JamesMahy commented May 30, 2019 •

edited

Loading

xorgnz commented Jun 27, 2019 •

edited

Loading