﻿---
title: Other command line parameters
description: Use silent, verbose, and related elasticsearch-plugin CLI options when installing plugins on self-managed clusters.
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/7959/deploy-manage/plugins-and-bundles/self-managed/other-command-line-parameters
products:
  - Elasticsearch
applies_to:
  - Self-managed Elastic deployments: Generally available
---

# Other command line parameters
The `elasticsearch-plugin` script supports additional command line parameters.

## Silent/verbose mode

The `--verbose` parameter outputs more debug information, while `--silent` turns off all output including the progress bar. The script may return the following exit codes:
<definitions>
  <definition term="0">
    Everything was OK
  </definition>
  <definition term="64">
    Unknown command or incorrect option parameter
  </definition>
  <definition term="74">
    IO error
  </definition>
  <definition term="70">
    Any other error
  </definition>
</definitions>


## Batch mode

Certain plugins require more privileges than those provided by default in core Elasticsearch. These plugins list the required privileges and ask for confirmation before continuing with installation.
When you run the plugin install script from another program (for example, install automation), the script should detect that it is not being called from a console and skip confirmation, automatically granting all requested permissions. If console detection fails, force batch mode with `-b` or `--batch`:
```sh
sudo bin/elasticsearch-plugin install --batch [pluginname]
```


## Custom config directory

If your `elasticsearch.yml` config file is in a custom location, specify the path to the config directory when using the plugin script:
```sh
sudo ES_PATH_CONF=/path/to/conf/dir bin/elasticsearch-plugin install <plugin name>
```


## Proxy settings

To install a plugin through a proxy, add the proxy details to the `CLI_JAVA_OPTS` environment variable with the Java settings `http.proxyHost` and `http.proxyPort` (or `https.proxyHost` and `https.proxyPort`):
```sh
sudo CLI_JAVA_OPTS="-Dhttp.proxyHost=host_name -Dhttp.proxyPort=port_number -Dhttps.proxyHost=host_name -Dhttps.proxyPort=https_port_number" bin/elasticsearch-plugin install analysis-icu
```

Or on Windows:
```sh
set CLI_JAVA_OPTS="-Dhttp.proxyHost=host_name -Dhttp.proxyPort=port_number -Dhttps.proxyHost=host_name -Dhttps.proxyPort=https_port_number"
bin\elasticsearch-plugin install analysis-icu
```