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

# Troubleshooting Request Connection

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

When configuring and running Flex 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 Flex Gateway and the
inbound connection between Flex Gateway and the client. Making direct requests isolates Flex 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 Flex Gateway and outbound connections are between Flex Gateway and the upstream service](/mulesoft/current/en-us/gateway/1.12/_images/flex-inbound-outbound-requests.png)

## Outbound Requests Between Flex Gateway and the Upstream Service

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

To make a direct outbound request to the upstream service:

1.  Log into the Flex 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 Flex Gateway

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

To make a direct inbound request to the client:

1.  Log into the Flex 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 Flex 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)