Cannot perform actions in slack ( acknowledge, resolve, ...), logs show 403 forbidden

[kakathinh42]

What went wrong?

What happened:

• I have deployed a docker stack "Grafana Oncall" with setting.hobby, setting env for Slack can integrate with Oncall.

• When I click to Resolve or Acknowledge an alert in Slack, It will show an error: This app responded with status code 403 but everything worked fine when I tried integrated with Telegram. Seems I can't curl with POST request to api_url: <ONCALL_ENGINE_PUBLIC_URL>/slack/interactive_api_endpoint/

What did you expect to happen:

• Can interact with the button Resolve, Silence, and Acknowledge on the Slack channel.

How do we reproduce it?

Click to button Resolve on the Slack channel
It will show "This app responded with status code 403"

Grafana OnCall Version

1.3.59

Product Area

Chatops

Grafana OnCall Platform?

Docker

User's Browser?

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36

Anything else to add?

logs:

2023-11-17 10:51:53 source=engine:app google_trace_id=none logger=django.request Forbidden: /slack/event_api_endpoint/
2023-11-17 10:51:53 source=engine:uwsgi status=403 method=POST path=/slack/event_api_endpoint/ latency=0.005135 google_trace_id=- protocol=HTTP/1.1 resp_size=262 req_body_size=3421
2023-11-17 10:51:54 source=engine:app google_trace_id=none logger=apps.slack.views Request id: None
2023-11-17 10:51:54 source=engine:app google_trace_id=none logger=root inbound latency=0.003852 status=403 method=POST path=/slack/event_api_endpoint/ user_agent=Slackbot 1.0 (+https://api.slack.com/robots) content-length=3421 slow=0 
2023-11-17 10:51:54 source=engine:app google_trace_id=none logger=django.request Forbidden: /slack/event_api_endpoint/
2023-11-17 10:51:54 source=engine:uwsgi status=403 method=POST path=/slack/event_api_endpoint/ latency=0.007409 google_trace_id=- protocol=HTTP/1.1 resp_size=262 req_body_size=3421

[kakathinh42]

Hello, anyone help me please :<

[kakathinh42]

When I dug into the config, I found I pasted the wrong SIGNGING_SECRECT on the Oncall configuration.