This message was deleted.
# atlantis-community
s
This message was deleted.
p
Hi team how do I troubleshoot the issue if /events is not trigger when a PR is raised. Currently I have a custom domain atantis.abc.com and I have deployed atlantis on AWS EKS. I see from the pod logs that the webhook URL /events is not triggered.
p
which version of atlantis?
p
atlnatis version is vv0.23.1. VCS is bitbucket . I have deployed in AWs EKS. When I check the atlantis pod logs , I see that /events URL is not hit when I comment on the PR.
I get to see only the following logs
Copy code
{"level":"info","ts":"2023-03-28T08:55:03.414Z","caller":"server/server.go:1030","msg":"Apply Lock: {false 0001-01-01 00:00:00 +0000 UTC }","json":{}}
{"level":"debug","ts":"2023-03-28T08:55:03.414Z","caller":"server/middleware.go:72","msg":"GET / – respond HTTP 200","json":{}}
{"level":"debug","ts":"2023-03-28T08:55:08.678Z","caller":"metrics/debug.go:47","msg":"gauge","json":{"name":"atlantis.scheduled.runtime.cpu.goroutines","value":8,"tags":{},"type":"gauge"}}
p
so then the webhook url is wrong, you need to add /events to it and your ingress should pass it down the pod without striping /events
p
I have a custom domain atlantis.abc.com. I have used the webhook URL as https://atlantis.abc.com/events and in my ingress rule I have used the path /events with the backend service updated to atlantis on port 80
p
then you should see calls to /events not /
there must be something wrong with the setup
p
I once again did the setup using the statefulset as mentioned here https://www.runatlantis.io/docs/deployment.html#kubernetes-manifests and used the service type loadbalancer. Currently, I see for the webhook requests but no build status showing next to the commit in the PR.
Copy code
Event	Details		Actions
pullrequest:updated	1 minute ago	
200
View details
repo:push	1 minute ago	
200
View details