---
schema_version: "1"
id: 9b9cccaf62631ec1275066a602f61a189641a1f72f1dde4a837c3b6cac855a8a
title: Troubleshooting Request Connection
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/troubleshoot-requests.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/troubleshoot-requests
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8fdb6182596c61eecd6929eaf58d29884eda7b0efbd9e1e9bbba5366bc1b33ab
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# 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/1.13/_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)