How to adjust webhook URL?

[larsassink]

Describe the bug
Unable to set the URL for the webhook properly.

To Reproduce
Steps to reproduce the behavior:

Follow Docker documentation and set the URL for the API.

Expected behavior
It gives me the following url: http://keep.example.com:8080/alerts/event instead of: http://keep.example.com/alerts/event

Additional context
docker-compose.yml:

services:
  keep-frontend:
    extends:
      file: docker-compose.common.yml
      service: keep-frontend-common
    image: us-central1-docker.pkg.dev/keephq/keep/keep-ui
    environment:
      - AUTH_TYPE=DB
      - NEXTAUTH_SECRET=1234
      - API_URL=https://keep.example.com
    volumes:
      - ./state:/state
    depends_on:
      - keep-backend

  keep-backend:
    extends:
      file: docker-compose.common.yml
      service: keep-backend-common
    image: us-central1-docker.pkg.dev/keephq/keep/keep-api
    environment:
      - AUTH_TYPE=DB
      - KEEP_JWT_SECRET=1234
      - PROMETHEUS_MULTIPROC_DIR=/tmp/prometheus
      - KEEP_METRICS=true
      - KEEP_HOST=keep-api.example.com
    volumes:
      - ./state:/state

docker-compose.common.yml:

services:
  keep-frontend-common:
    ports:
      - "3000:3000"
    environment:
      - NEXTAUTH_SECRET=1234
      - NEXTAUTH_URL=https://keep.example.com
      - NEXT_PUBLIC_API_URL=https://keep-api.example.com
      - POSTHOG_KEY=phc_muk9qE3TfZsX3SZ9XxX52kCGJBclrjhkP9JxAQcm1PZ
      - POSTHOG_HOST=https://ingest.keephq.dev
      - NEXT_PUBLIC_SENTRY_DSN=https://0d4d59e3105ffe8afa27dcb95a222009@o4505515398922240.ingest.us.sentry.io/4508258058764288
      - PUSHER_HOST=localhost
      - PUSHER_PORT=6001
      - PUSHER_APP_KEY=keepappkey

  keep-backend-common:
    ports:
      - "8080:8080"
    environment:
      - PORT=8080
      - SECRET_MANAGER_TYPE=FILE
      - SECRET_MANAGER_DIRECTORY=/state
      - DATABASE_CONNECTION_STRING=sqlite:////state/db.sqlite3?check_same_thread=False
      - OPENAI_API_KEY=$OPENAI_API_KEY
      - PUSHER_APP_ID=1
      - PUSHER_APP_KEY=keepappkey
      - PUSHER_APP_SECRET=keepappsecret
      - PUSHER_HOST=keep-websocket-server
      - PUSHER_PORT=6001
      - USE_NGROK=false

[dosubot[bot]]

Hello @larsassink! I'm Dosu, here to help you solve bugs, answer questions, and assist you in becoming a contributor. While we wait for a human maintainer, feel free to share more details about your issue!

The issue you're experiencing with the URL configuration seems to be related to the port specification in the docker-compose setup. The URL http://keep.example.com:8080/alerts/event includes the port 8080, which is likely due to the port mapping defined in your docker-compose.common.yml for the keep-backend-common service:

ports:
  - "8080:8080"

To achieve the expected URL http://keep.example.com/alerts/event without the port number, you need to ensure that the backend service is accessible on the default HTTP port (port 80) or HTTPS port (port 443). Here are a few steps you can take:

1. Change Port Mapping: Modify the port mapping in your docker-compose.common.yml to use port 80 or 443. For example:

   ports:
     - "80:8080"

   or

   ports:
     - "443:8080"

2. Reverse Proxy Configuration: If you are using a reverse proxy (like Nginx or Traefik), configure it to route requests to the backend service without exposing the port number in the URL.

3. Environment Variable: Ensure that the KEEP_API_URL environment variable in the keep-backend service is set correctly to reflect the desired URL without the port number, if applicable.

These changes should help you achieve the URL format you expect. If you are using a reverse proxy, make sure it is correctly configured to handle requests on the desired port and route them to the backend service.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[shahargl]

Hey @larsassink, you can adjust the URL by changing the PORT env var to be 80 like you want

[larsassink]

Yeah, tried that as well but when accessing the incoming webhook settings in keep it now gives this URL: http://keep-api.domain.com:80/alerts/event.

I need that :80 part to be removed since my other services do not seem to work with that in place.

[shahargl]

@larsassink ok - you can use KEEP_API_URL and just put there whatever you want, and Keep will use that

[shahargl]

@larsassink converted to discussion

[larsassink]

Alright, thanks! It does seem to be working, even though it has port 80 in the url. I forgot to update the webhooks in the provider settings.