---
schema_version: "1"
id: 75aafa47c0cdaa6f0184b6ecc34b46b64aef02daa336866edcbf2efe1adaa5ec
title: Troubleshooting Platform Connections
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/troubleshoot-platform-connection.md
canonical_url: https://docs.mulesoft.com/gateway/latest/troubleshoot-platform-connection
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d1deb0019f28c8e3620062cf0308495cd5c79f3d99b12f14212f56cd605a25c6
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Troubleshooting Platform Connections

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

When configuring Omni Gateway, it is possible for the Omni Replica’s `registration.yaml` to be
absent or for the replica to lose its connection to Anypoint Platform.

To troubleshoot whether a registration file is present and whether Omni Gateway can make platform
connections, use the following command:

```ssh
flexctl check connections
```

The `flexctl check connections` command first ensures that a `registration.yaml` file is present.
Then it checks whether the replica can connect to the URLs defined in the registration file. If the
`flexctl check connections` command is successful, it returns the following `info` message:

$ flexctl check connections \[flexctl\]\[info\] Connection to platform endpoints successful.

## No Registration File Found

If the `registration.yaml` file isn’t found, Omni Gateway returns the following error message:

$ flexctl check connections Error: no registration config

To troubleshoot an absent registration file, check your Omni Replica configuration folder. To learn
more about registering an Omni Gateway, see following section for your relevant mode:

- [Registering and Running Omni Gateway in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-reg-run)

- [Registering and Running Omni Gateway in Local Mode](https://docs.mulesoft.com/gateway/latest/local-reg-run)

## Failed Connection

There are multiple reasons why Omni Gateway might experience connection issues, such as an error in
the gateway’s environment or a network issue. How you troubleshoot your error depends on the error
returned.

If Omni Gateway can’t connect to a specific URL, it returns an error message that includes the
unreachable URL and the error message returned from the connection attempt. The following error
message is an example of an error returned due to no internet connection:

$ flexctl check connections Error: failed connecting to https://anypoint.mulesoft.com/: dial tcp
52.22.227.22:443: connect: network is unreachable

## See Also

- [Troubleshooting Registration Issues](https://docs.mulesoft.com/gateway/latest/troubleshoot-reg)

- [Troubleshooting Request Connection](https://docs.mulesoft.com/gateway/latest/troubleshoot-requests)

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