---
schema_version: "1"
id: c5dd35fe8a4d5b0264e748892b017fdebdae3a2e57c4073b3e5f61f47a60810f
title: Troubleshooting Docker Command Issues
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.9/flex-troubleshoot-docker.md
canonical_url: https://docs.mulesoft.com/gateway/1.9/flex-troubleshoot-docker
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3d479e14fb74bf79bea6efe03af8d6ed7d07a779f6311504a2e41e1e66fe7715
description: MuleSoft Documentation Site
release: "1.9"
latest: false
---
---
product: Omni Gateway
version: 1.9
---

# Troubleshooting Docker Command Issues

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

Troubleshoot errors returned by a `docker` command:

- [Docker Is Not Started](#daemon-bad-response)

- [Reg Facade Error (400 Bad Request)](#bad-request)

## Docker Is Not Started

If Docker is not started, a `docker` command returns an error message similar to the following ones:

- Error response from daemon: Bad response from Docker engine

- ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon
  running?

If you get this error, start Docker.

## Reg Facade Error (400 Bad Request)

The following error can occur when you use `docker run` to register your gateway:

\[flexctl\]\[error\] reg facade call returned error response: HTTP/1.1 400 Bad Request

The reason for this error is available within the error message. Common causes include:

- `an active target with the same name already exists in this organization and environment`

  To avoid this issue, provide a _unique name_ for your gateway when running the registration
  command. Note that you _cannot reuse the same name_ even if a previous registration with that name
  was successful. When this error occurs, the command generates an _empty_ `registration.yaml`,
  which prevents re-registration _and_ produces an error when you try to use the file when deploying
  the gateway to your cluster.

- `no valid registration token was found`

  To avoid this issue, generate a new token for the command by refreshing the **Add a Flex Gateway**
  page for Kubernetes and rerun the registration command.

## See Also

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

- [Troubleshooting with the CLI](https://docs.mulesoft.com/gateway/1.9/flex-troubleshoot-admin-api)

- [Setting Up Self-Managed Flex Gateway](https://docs.mulesoft.com/gateway/1.9/flex-gateway-set-up)

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