# 400 Bad Request when Exposing external HTTPS service

**URL:** <https://discuss.konghq.com/t/400-bad-request-when-exposing-external-https-service/9732>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [February 2, 2022, 2:46pm UTC](https://discuss.konghq.com/t/400-bad-request-when-exposing-external-https-service/9732 "2022-02-02T14:46:13Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![traines](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/traines/32/158_2.png) [@traines](https://discuss.konghq.com/u/traines)\
**Post date:** [February 7, 2022, 7:06pm UTC](https://discuss.konghq.com/t/400-bad-request-when-exposing-external-https-service/9732/10 "2022-02-07T19:06:47Z")

</div>

SRV answer is in the other thread: [Direct traffic to AWS ECS services using SRV records](https://discuss.konghq.com/t/direct-traffic-to-aws-ecs-services-using-srv-records/9757)

Lack of change is odd, is it still showing up as HTTP when you inspect the admin API, with no errors in the controller logs indicating that the sync failed?

---

_[View the full topic](https://discuss.konghq.com/t/400-bad-request-when-exposing-external-https-service/9732)._