Error sending message: Post "***": unsupported protocol scheme ""

Question

Error sending message: Post "***": unsupported protocol scheme ""

Closed this issue 2 years ago · 6 comments

Hello Everyone,Can anyone help me its working before but suddenly its failing & getting this error.

jobs:
slackNotification:
name: Slack Notification
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Slack Notification
uses: rtCamp/action-slack-notify@v2
env:
SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}

can anyone tell me what we need to be fix this above issue.

Answer 1 · 2021-10-07T15:37:25.000Z

any update ?
i got same error

Answer 2 · 2021-10-08T03:07:24.000Z

issue resolved

@riteshgetsetup please include https://hooks.slack.com/services/

Answer 3 · 2022-02-20T21:34:57.000Z

I got the same error because I try to create a App Token on Slack configuration and try to use that token as the SLACK_WEBHOOK.

I solved the error after installing the "Incomming Webhooks" app into my slack, here's the link.
After installing the app, I just select the channel and got the webhook uri

This URI need to be placed into the GitHub repo settings on the secrets section. See the documentation

Hoping I can help somebody.

Answer 4 · 2022-04-13T09:43:48.000Z

Closing this issue as it is resolved.

Answer 5 · 2022-10-11T05:20:26.000Z

I had the same problem in two Apps I created. I solved the problem by adding a secret variable, and adding to it the path of the webhook created in my App.
Slack:
url: https://api.slack.com/apps/your-app
Features > Incoming Webhooks > Webhook Url
Github:

Answer 6 · 2023-07-31T17:07:38.000Z

Note for others:
I've been using rtCamp/action-slack-notify for years and only just encountered this issue.

Last week I was receiving: Error sending message: Error on message: 404 Not Found, but then it changed to: Error sending message: Post "***": unsupported protocol scheme ""... The webhook URL was good as I could curl into it, and the value was checked for leading/trailing spaces, having re-pasted the same value in a few times with no luck. Note specifically that this incoming webhook was working with other jobs... Just this one with a new secret was sticking.

Today the issues persisted until re-saving the webhook secret with the same value again worked for no apparent reason. Crud in the works... It's not you, it's Git.