# Problem with Kong OSS 3.9.1 on port 8443

**URL:** <https://discuss.konghq.com/t/problem-with-kong-oss-3-9-1-on-port-8443/13959>\
**Category:** Questions\
**Tags:** kong-gateway\
**Created:** [May 5, 2026, 12:53am UTC](https://discuss.konghq.com/t/problem-with-kong-oss-3-9-1-on-port-8443/13959 "2026-05-05T00:53:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Milton\_Valenzano](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/milton_valenzano/32/3598_2.png) [@Milton\_Valenzano](https://discuss.konghq.com/u/Milton_Valenzano)\
**Post date:** [May 5, 2026, 12:53am UTC](https://discuss.konghq.com/t/problem-with-kong-oss-3-9-1-on-port-8443/13959/1 "2026-05-05T00:53:43Z")

</div>

Hello.

I have a question. I currently have Kong OSS version 3.9.1 installed with PostgreSQL version 17 an on-premises machine, and the certificates are installed. When I use the address [https://nameserver:8443](https://nameserver:8443), I get a 404 error, but if I use the address [https://nameserver:8443/route](https://nameserver:8443/route), it works without problems. I’ve reinstalled Kong and applied several configurations, but the error persists. Does anyone know how I could fix this problem or have any ideas about which Red Hat configuration I should check?

In addition to this issue, I’ve tried routing port 8444 by simulating API Lookback, but it doesn’t work.

---

<div class="post-metadata">

**Author:** ![rick](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/rick/32/4446_2.png) [@rick](https://discuss.konghq.com/u/rick)\
**Post date:** [May 5, 2026, 2:54pm UTC](https://discuss.konghq.com/t/problem-with-kong-oss-3-9-1-on-port-8443/13959/3 "2026-05-05T14:54:54Z")

</div>

@Milton_Valenzano I ran your question through our AI chat capaibilty in the documentation site. I hope this is useful. For further questions you may find it helpful to begin with the AI agent there and then come to the forums if you cannot find a good answer. Best of luck

> **[Kong Docs](https://developer.konghq.com/)**
>
> Documentation for Kong, the Cloud Connectivity Company for APIs and Microservices.

* * *

## Understanding Your 404 on `https://nameserver:8443`

The behavior you’re describing is actually **expected** in Kong Gateway. When you hit `https://nameserver:8443` (the root path `/`) with no routes configured to match it, Kong returns a 404 with `{"message":"no Route matched with those values"}`. [[Test connectivity to Kong](https://developer.konghq.com/kubernetes-ingress-controller/install/#test-connectivity-to-kong)]

Your specific route at `/route` works because Kong has a matching rule for that path. The root `/` simply has no matching route defined.

### How to Fix the Root Path 404

You can create a **fallback route** that catches all unmatched paths by defining a route with the path `/`. Since all URIs are prefixed by `/`, this route will have the lowest priority and only match requests that don’t match any other route. [[Configure fallback route](https://developer.konghq.com/how-to/configure-fallback-route/#create-a-fallback-gateway-service-and-route)]

```auto
_format_version: "3.0"
services:
  - name: fallback_service
    url: http://your-upstream-service.com
routes:
  - name: fallback_route
    service:
      name: fallback_service
    paths:
    - "/"
    protocols:
    - http
    - https

```

Apply it with:

```auto
deck gateway apply -

```

Replace `http://your-upstream-service.com` with your actual upstream URL.

* * *

### Regarding Port 8444 (Admin API)

Port `8444` is the **Admin API HTTPS port** , not a proxy port. It is used for managing Kong Gateway (e.g., via `kong.conf`’s `admin_listen` setting), not for proxying API traffic. [[Kong Gateway ports](https://developer.konghq.com/gateway/network/)] Routing API traffic through it is not its intended purpose, which is likely why your “API Lookback” simulation isn’t working as expected.

* * *

### Red Hat / OS-Level Checks

The knowledge sources do not contain specific Red Hat configuration guidance. However, based on Kong’s documentation, ensure your firewall allows traffic on the ports you’re using (e.g., `8443` for HTTPS proxy). [[Kong Gateway ports](https://developer.konghq.com/gateway/network/)]

If you’re still seeing issues after creating the fallback route, the problem is likely in your route configuration rather than the OS or Kong installation itself.

---

<div class="post-metadata">

**Author:** ![Milton\_Valenzano](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/milton_valenzano/32/3598_2.png) [@Milton\_Valenzano](https://discuss.konghq.com/u/Milton_Valenzano)\
**Post date:** [May 5, 2026, 3:34pm UTC](https://discuss.konghq.com/t/problem-with-kong-oss-3-9-1-on-port-8443/13959/4 "2026-05-05T15:34:24Z")

</div>

```auto

```

You’re right. But in my case, I’m trying to apply API Lookback to Kong OSS. My question is whether it only works with port 8001 because it doesn’t work with port 8444.