Remove JFrog CLI Server Configurations

jf config rm (remove) deletes one or all server entries from your local JFrog CLI configuration. Removing a server clears stored credentials for that ID. Omitting the server ID removes every configured server. Use --quiet to skip the confirmation prompt in an interactive terminal.

This topic covers:

• Remove a specific server
• Remove all servers
• Recover after removing the active server

Synopsis

jf config rm <server-id>

Aliases: jf c rm

Where:

• <server-id>: Optional. When provided, only that server is removed. When omitted, all servers are removed. Append flags such as --quiet as needed.

Arguments

The following table describes command arguments.

Options

The following table describes command options.

Examples

Remove a Specific Server

To remove a specific server:

1. Run:

   Bash

   jf config rm <server-id> --quiet

   Where:

   • <server-id>: The ID of the server to remove.

   For example:

   Bash

   jf config rm staging-server --quiet

2. Confirm the configuration. No output is printed on success.

To verify the removal:

• Run:

  Bash

  jf config show

Remove All Servers

To remove all configured servers:

1. Run:

   Bash

   jf config rm --quiet

2. Confirm that no servers remain. No output is printed on success.

To verify all configurations are gone:

• Run:

  Bash

  jf config show

  Expected: empty output (no servers configured).

Recover After Removing the Active Server

If you removed the currently active server, another server must become the default before JFrog CLI commands target a platform.

To set a different server as the active default:

• Run:

  Bash

  jf config use <other-server-id>

  Where:

  • <other-server-id>: A server ID that remains in your configuration.

  For example:

  Bash

  jf config use dev-server

Important Notes

• Destructive action. Removing a server configuration deletes its stored credentials permanently. You cannot undo this. After removing, run jf config show to confirm the expected servers are no longer listed.
• Remove all. Omitting the server ID removes all stored configurations. The --quiet flag skips the confirmation prompt. JFrog CLI does not detect a non-interactive shell on its own. The prompt is auto-suppressed only when the CI environment variable is set to true. A script that sets neither CI=true nor --quiet still hits the prompt. Since no input reaches it, JFrog CLI defaults to "no" (nothing is removed) yet the command still exits 0. Confirm the outcome with jf config show rather than relying on the exit code alone.
• Active server. If you remove the active (default) server, there is no active server until you run jf config use <other-id> or add a new one with jf config add.
• CI/CD cleanup. In pipelines, add jf config rm <server-id> --quiet as a teardown step to avoid leaking credentials in ephemeral environments.
• Non-existent server ID. If the specified server-id does not exist, the JFrog CLI prints an informational message and exits 0. Confirm your server ID with jf config show before you run remove in automation scripts.
• Empty output after remove all. After removing all servers, jf config show returns empty output with exit code 0. This is expected. It does not indicate an error.

Frequently Asked Questions

This section provides answers to frequently asked questions.

Related Topics

• Add a JFrog CLI Server Configuration
• Set Active JFrog CLI Server
• Show JFrog CLI Server Configurations
• Manage Server Configurations