---
schema_version: "1"
id: 4fbe8c1cca6997b1548f7f178247788cc08fd83b796e87546c6f43bebe4b0c2f
title: Troubleshooting Request Connection
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/troubleshoot-requests.md
canonical_url: https://docs.mulesoft.com/gateway/latest/troubleshoot-requests
source_site: docs.mulesoft.com
content_type: documentation
content_hash: f229da6b024ae45ae098be260b83506870acbffea802238645aa7bd66ed8429e
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Troubleshooting Request Connection

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When configuring and running Omni Gateway, you might encounter connection issues.

To troubleshoot these issues, use the `flexctl check http` command. This command makes direct
requests to both the outbound connection between the upstream service and Omni Gateway and the
inbound connection between Omni Gateway and the client. Making direct requests isolates Omni Gateway
connections, which allows you to localize the issue.

The following diagram demonstrates the difference between inbound and outbound requests.

![Inbound connections are between the client and Omni Gateway and outbound connections are between Omni Gateway and the upstream service](/mulesoft/current/en-us/gateway/latest/_images/inbound-outbound-requests.png)

## Outbound Requests Between Omni Gateway and the Upstream Service

Isolating the connection between the upstream service and Omni Gateway enables you to test for
connection between the two.

To make a direct outbound request to the upstream service:

1.  Log into the Omni Gateway container or VM:

    - Linux:

      ```ssh
      ssh [-i sshkey.pem] <user>@<domain>
      ```

    - Docker:

      ```ssh
      docker exec -it <container-id> bash
      ```

    - Kubernetes:

      ```ssh
      kubectl -n <namespace> exec -it <pod-name> -- bash
      ```

2.  Make a request to the upstream service:

    ```ssh
    flexctl check http -X=POST -d='{\"key\": \"value\"}' -H='Authorization:token' <http://upstream.domain>
    ```

## Inbound Requests Between the Client and Omni Gateway

Isolating the connection between Omni Gateway and the client enables you to test if the connection
issue is due to a load balancer or another system added between Omni Gateway and the client.

To make a direct inbound request to the client:

1.  Log into the Omni Gateway container or VM:

    - Linux:

      ```ssh
      ssh [-i sshkey.pem] <user>@<domain>
      ```

    - Docker:

      ```ssh
      docker exec -it <container-id> bash
      ```

    - Kubernetes:

      ```ssh
      kubectl -n <namespace> exec -it <pod-name> -- bash
      ```

2.  Make a request to Omni Gateway:

    ```ssh
    flexctl check http -X=POST -d='{\"key\": \"value\"}' -H='Authorization:token' http://localhost:<api-instance-port>/<path>
    ```

## See Also

- [Known Issues](https://help.salesforce.com/s/issues)