Sentry Slack integration exit code 1 docker

[ezols]

Hi,

My setup, sentry(on docker) and nginx reverse proxy(on host) which terminates ssl and then forwards it to localhost:9000
Only thing i have changed in docker-compose.yml is "- “127.0.0.1:$SENTRY_BIND:80/tcp” added 127.0.0.1

The problem:
Im trying to integrate sentry to slack, in config.yml file i have added secrets like this:

slack.client-id: <‘12222222222.211111111111146’>
slack.client-secret: <‘zxczxc12321123asdasdasdsd’>
slack.signing-secret: <‘zxczxzxcasdasdasd12312132’>

After starting up sentry with made changes i see that multiple containers are exiting with status code 1:

Sentry itself looks like working, but when i try to add slack in sentry i still get this:

“Something went wrong when authorizing this app.”
Error details
Invalid client_id parameter

What am i doing wrong?

Thanks

[BYK]

Can you share your config.yml file as it is? Looks like you have an error in it. You’ll need to mask your secrets in it tho/

[ezols]

Good morning!

I managed to connect sentry to slack, but the issue now is that none of the events are sent to slack via configured sentry slack bot.

# While a lot of configuration in Sentry can be changed via the UI, for all
# new-style config (as of 8.0) you can also declare values here in this file
# to enforce defaults or to ensure they cannot be changed via the UI. For more
# information see the Sentry documentation.

###############
# Mail Server #
###############

# mail.backend: 'smtp'  # Use dummy if you want to disable email entirely
mail.host: 'smtp'
# mail.port: 25
# mail.username: ''
# mail.password: ''
# mail.use-tls: false
# The email address to send on behalf of
# mail.from: 'root@localhost'

# If you'd like to configure email replies, enable this.
# mail.enable-replies: true

# When email-replies are enabled, this value is used in the Reply-To header
# mail.reply-hostname: ''

# If you're using mailgun for inbound mail, set your API key and configure a
# route to forward to /api/hooks/mailgun/inbound/
# Also don't forget to set `mail.enable-replies: true` above.
# mail.mailgun-api-key: ''

###################
# System Settings #
###################

# If this file ever becomes compromised, it's important to generate a new key.
# Changing this value will result in all current sessions being invalidated.
# A new key can be generated with `$ sentry config generate-secret-key`
system.secret-key: 'fxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'

# The ``redis.clusters`` setting is used, unsurprisingly, to configure Redis
# clusters. These clusters can be then referred to by name when configuring
# backends such as the cache, digests, or TSDB backend.
# redis.clusters:
#   default:
#     hosts:
#       0:
#         host: 127.0.0.1
#         port: 6379

################
# File storage #
################

# Uploaded media uses these `filestore` settings. The available
# backends are either `filesystem` or `s3`.

filestore.backend: 'filesystem'
filestore.options:
  location: '/data/files'
dsym.cache-path: '/data/dsym-cache'
releasefile.cache-path: '/data/releasefile-cache'

# filestore.backend: 's3'
# filestore.options:
#   access_key: 'AKIXXXXXX'
#   secret_key: 'XXXXXXX'
#   bucket_name: 's3-bucket-name'

system.internal-url-prefix: 'http://web:9000'
symbolicator.enabled: true
symbolicator.options:
  url: "http://symbolicator:3021"

transaction-events.force-disable-internal-project: true

######################
# GitHub Integration #
######################

# github-login.extended-permissions: ['repo']
# github-app.id: GITHUB_APP_ID
# github-app.name: 'GITHUB_APP_NAME'
# github-app.webhook-secret: 'GITHUB_WEBHOOK_SECRET' # Use only if configured in GitHub
# github-app.client-id: 'GITHUB_CLIENT_ID'
# github-app.client-secret: 'GITHUB_CLIENT_SECRET'
# github-app.private-key: |
#   -----BEGIN RSA PRIVATE KEY-----
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   -----END RSA PRIVATE KEY-----

#####################
# Slack Integration #
#####################

# Refer to https://develop.sentry.dev/integrations/slack/ for setup instructions.

slack.client-id: 'xxxxxxxxxxxxxxxxxxx'
slack.client-secret: 'xxxxxxxxxxxxxxxxxxxx'
slack.signing-secret: 'xxxxxxxxxxxxxxxxxx'
## If legacy-app is True use verfication-token instead of signing-secret
# slack.verification-token: <verification token>
system.url-prefix: "https://sentry.xxxxxxxxx.lv"

From Slack:

This is what happens when i send test event.

Please let me know what else do you need to resolve this problem.

Thank you.