---
schema_version: "1"
id: f3b11218ca40da662e7a23cc0107ccf6ec317f99bc5a87e291ec434618646df0
title: Troubleshooting Linux Permissions
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/troubleshoot-linux-permissions.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/troubleshoot-linux-permissions
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 69ab16f0561f06c60d20e359f7fc05d05d9bcb4e37ca335598034de0ab3d5470
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# Troubleshooting Linux Permissions

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

To help limit access to information about an Omni Gateway, the following `flexctl` commands can be
executed on Linux deployments only by the root user and by users in the `flex` user group:

- `flexctl dump`

- `flexctl version`

- `flexctl check connections`

- `flexctl probe`

- `flexctl registration inspect` (when executed without the `--file` flag)

There are two options to execute these commands:

- [Add the User to the flex User Group](#add-user-to-flex-group)

- [Run as the Root User](#run-as-root-user)

## Add the User to the flex User Group

Adding a user to the `flex` user group is a permanent solution and requires no action after the user
is added. Execute the following command to add the current user to the `flex` user group:

```ssh
sudo usermod -a -G flex $USER
```

After running the command, the user must log in to the VM again to begin using the `flexctl`
commands.

## Run as the Root User

Executing the `sudo` command with your `flexctl` command is the quickest way to access Omni Gateway
information. However, you must execute the `sudo` command every time you run a `flexctl` command if
the user is not part of the `flex` user group:

```ssh
sudo flexctl <command>
```

When the `sudo flexctl dump` command is executed, the root user is the owner of the created dump
files. If the current user is not the root user, the user cannot view the dumped files. To view the
files, execute the following command to change the owner of the files:

```ssh
sudo chown $USER *.json
```

Files in the `conf.d` directory must have `644` permissions, allowing the owner to read and write,
and the group and others to read.

## See Also

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

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