Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

api_key is required to use webhooks #2482

Closed
v57 opened this issue Feb 14, 2024 · 1 comment
Closed

api_key is required to use webhooks #2482

v57 opened this issue Feb 14, 2024 · 1 comment

Comments

@v57
Copy link

v57 commented Feb 14, 2024

Describe the bug
LiveKit server not starts when I enable webhooks with api_key and urls. It throws an error api_key is required to use webhooks. I tried different values and always getting same error. I have docker-compose and config yaml so it would be easy to reproduce

Server

  • Version: 1.5.2
  • Environment: Docker
  • any other information about your deployment setup

To Reproduce
Here is my livekit.yaml

port: 7880
bind_addresses:
    - ""
rtc:
    tcp_port: 7881
    port_range_start: 50000
    port_range_end: 60000
    use_external_ip: false
    enable_loopback_candidate: false
redis:
    address: redis:6379
keys:
    KEY: SECRETSECRETSECRETSECRETSECRETSECRET
webhook:
  api_key: 'mywebhook'
  urls:
    - 'website.com/webhook'

And docker-compose.yaml

version: '3.8'
services:
  livekit:
    image: livekit/livekit-server:v1.5.2
    command: --config /etc/livekit.yaml
    volumes:
      - ./livekit.yaml:/etc/livekit.yaml
  redis:
    image: redis:alpine
@v57
Copy link
Author

v57 commented Feb 14, 2024

I see, api_key should be equal to key in keys, so setting api_key: KEY actually starts the server.
Maybe it's better to change error log to api_key name not found in provided keys

@v57 v57 closed this as completed Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant