Skip to content
Cloud Plugin Marketplace

Troubleshooting

Installation issues

Section titled “Installation issues”

Marketplace not found

Section titled “Marketplace not found”

Symptom: Error when trying to install plugins from the marketplace.

Solution:

Terminal window
# Verify the marketplace is added
/plugin marketplace list


# Re-add if necessary
/plugin marketplace remove f5-distributed-cloud
/plugin marketplace add robinmordasiewicz/f5xc-marketplace

Plugin installation fails

Section titled “Plugin installation fails”

Symptom: Error during plugin installation.

Cause: Network connectivity issues, inaccessible plugin repository, or outdated Claude Code version.

Solution:

Check network connectivity:

Terminal window
curl -I https://github.com/robinmordasiewicz/f5xc-console

Try direct installation:

Terminal window
/plugin install robinmordasiewicz/f5xc-console

Update Claude Code:

Terminal window
npm update -g @anthropic-ai/claude-code

Commands not appearing

Section titled “Commands not appearing”

Symptom: Plugin installed but commands not available.

Solution:

  1. Restart Claude Code after plugin installation
  2. Verify the plugin is enabled:
Terminal window
/plugin list

Browser automation issues

Section titled “Browser automation issues”

Chrome extension not connected

Section titled “Chrome extension not connected”

Symptom: Browser commands fail with connection errors.

Solution:

  1. Verify the Claude in Chrome extension is installed
  2. Check the extension is enabled in Chrome
  3. Verify MCP connection in Claude Code settings

Login timeout

Section titled “Login timeout”

Symptom: /xc:console login times out before completing authentication.

Cause: Slow network connection, Azure AD authentication delays, or blocked browser popup.

Solution:

  1. Increase timeout in plugin settings
  2. Check for blocked popups in Chrome
  3. Manually complete authentication if needed
Section titled “Navigation fails”

Symptom: /xc:console nav cannot find the target page.

Solution:

  1. Run crawl to update navigation metadata:

    Terminal window
    /xc:console crawl https://your-tenant.console.ves.volterra.io

  2. Verify you are logged into the correct tenant

  3. Check that the target exists in your namespace

Session expired

Section titled “Session expired”

Symptom: Commands fail after a period of inactivity.

Solution:

Re-authenticate:

Terminal window
/xc:console login https://your-tenant.console.ves.volterra.io

Configuration issues

Section titled “Configuration issues”

Wrong tenant

Section titled “Wrong tenant”

Symptom: Commands affect unexpected resources.

Solution:

  1. Verify the current session:

    Terminal window
    /xc:console status

  2. Log in to the correct tenant:

    Terminal window
    /xc:console login https://correct-tenant.console.ves.volterra.io

Namespace mismatch

Section titled “Namespace mismatch”

Symptom: Resources not found or created in wrong namespace.

Solution:

Navigate to the correct namespace before creating resources:

Terminal window
/xc:console nav namespace my-namespace

Performance issues

Section titled “Performance issues”

Slow command execution

Section titled “Slow command execution”

Symptom: Commands take longer than expected.

Cause: Large DOM in the console, network latency, or complex page rendering.

Solution:

  1. Wait for the page to fully load
  2. Reduce concurrent operations
  3. Use the CLI plugin for batch operations (when available)

Memory usage

Section titled “Memory usage”

Symptom: Browser becomes unresponsive.

Solution:

  1. Close unnecessary browser tabs
  2. Restart Chrome periodically during long sessions
  3. Monitor Chrome memory in Task Manager

Getting more help

Section titled “Getting more help”

Gather diagnostic information

Section titled “Gather diagnostic information”

When reporting issues, include:

  1. Claude Code version:

    Terminal window
    claude --version

  2. Plugin version:

    Terminal window
    /plugin list

  3. Chrome version: Check chrome://version

  4. Error messages: Full error text or screenshot

  5. Steps to reproduce: Commands that led to the issue

Report an issue

Section titled “Report an issue”
  1. Search existing issues
  2. If not found, create a new issue
  3. Use the bug report template
  4. Include diagnostic information

Community support

Section titled “Community support”
  • GitHub Discussions (coming soon)
  • Stack Overflow tag: f5-distributed-cloud

Frequently asked questions

Section titled “Frequently asked questions”

Can I use this with multiple tenants?

Section titled “Can I use this with multiple tenants?”

Yes. Switch between tenants by logging in to different URLs:

Terminal window
/xc:console login https://tenant1.console.ves.volterra.io
# ... work on tenant 1 ...
/xc:console login https://tenant2.console.ves.volterra.io
# ... work on tenant 2 ...

Are my credentials stored?

Section titled “Are my credentials stored?”

No credentials are stored by the plugins. Authentication is handled through Azure AD SSO with session cookies managed by Chrome.

Can I automate without a browser?

Section titled “Can I automate without a browser?”

The f5xc-cli and f5xc-api plugins (planned) provide headless automation. See the Roadmap for availability.

How do I update plugins?

Section titled “How do I update plugins?”
Terminal window
/plugin update f5xc-console

Or reinstall to get the latest version.