← Support Knowledge Base

Troubleshooting Pistachio

Common problems and how to fix them. If you don't find your issue here, open a ticket.

Wallet Errors

"No wallet configured"

Pistachio needs a wallet to interact with the Morpheus network. From the CLI:

pistachio config set private-key

Paste your wallet key when prompted. It is stored locally with restricted file permissions and never leaves your machine. The desktop app walks you through this on first launch.

If you already set it and still see this, check that the config file exists:

cat ~/.pistachio/config.toml | grep -i key

If the file is missing or empty, run the setup again.

"No DRM3Pass found"

You need a Pistachio Pass NFT on Base to stake MOR and use inference. The Starter pass is free (less than $0.01 in gas).

Claim one at nft.drm3.xyz or run:

pistachio claim-pass

Make sure you claim using the same wallet address that Pistachio is configured with. Check your configured address:

pistachio config show

If you claimed with a different wallet, either reclaim with the correct wallet or reconfigure Pistachio to use the wallet that holds the pass.

"Invalid private key" or wallet address mismatch

The key you pasted may have extra whitespace, a missing prefix, or be the wrong format. Your wallet key should be a 64-character hex string (with or without the 0x prefix). Reset and try again:

pistachio config set private-key
Trust Wallet overrides MetaMask in Chrome

If you have both MetaMask and Trust Wallet browser extensions installed, Trust Wallet can hijack wallet connections. Symptoms: clicking "Connect Wallet" opens Trust Wallet instead of MetaMask, or transactions go to the wrong wallet.

Fix: Go to chrome://extensions in your browser and disable the Trust Wallet extension. Refresh the page. MetaMask will now handle all wallet connections correctly.

This is a known conflict between the two extensions. They both try to control the same browser API (window.ethereum). Only one can be active at a time.

MOR and ETH Balance

"Insufficient MOR balance"

MOR must be on the Base network. MOR on Ethereum mainnet or Arbitrum will not work. If you purchased MOR before it moved to Base, you need to bridge it.

Check your balance:

pistachio wallet balance

To get MOR on Base:

"Insufficient ETH for gas"

Staking transactions require a small amount of ETH on Base for gas fees. $5 worth of ETH is more than enough for many sessions. Send ETH to your wallet on the Base network.

If you have ETH on Ethereum mainnet, bridge it to Base using the Base Bridge.

"Approval required" or "MOR allowance too low"

Before staking, the MOR token contract needs permission to let the Morpheus session contract move your tokens. Run:

pistachio wallet approve

This is a one-time transaction. After approval, staking will work normally.

Sessions

Sessions expiring quickly

Session duration depends on your stake amount relative to the provider's minimum. When your stake runs low, the session closes. Options:

MOR is collateral, not payment. Your full stake is returned when the session closes.

To manually refresh all sessions:

pistachio session renew-all
Session open fails or hangs

This is usually an RPC issue. Public RPCs rate-limit staking transactions and cause timeouts. Add a free Alchemy RPC key:

  1. Create a free Alchemy account
  2. Create an app on Base Mainnet
  3. Add to ~/.pistachio/config.toml:
base_rpc_urls = "https://base-mainnet.g.alchemy.com/v2/YOUR_KEY"

Then restart Pistachio.

"Session not found" or stale session data

If Pistachio shows sessions that no longer exist on-chain, refresh the session list:

pistachio session list

If sessions are stuck in a pending state, check that your RPC connection is healthy and try closing them explicitly:

pistachio session close --session 0x...

Models and Inference

Models not loading or empty model list

Refresh the model catalog from on-chain data, then probe providers to check availability:

pistachio catalog refresh
pistachio catalog probe

If the catalog is still empty, check your RPC connection. An unreliable RPC will cause catalog discovery to fail silently.

Inference returning errors or timing out

Check that your session is active and the provider is healthy:

pistachio session list

If the session shows as active but inference fails, the provider may be down. Open a session with a different provider for the same model:

pistachio catalog filter --healthy

This shows which models have healthy providers right now. You can also check overall network health:

Network status
status.drm3.network
"Unknown model" in dashboard

This means the model ID from the provider does not match Pistachio's known model list. Refresh the catalog:

pistachio catalog refresh

If the model still shows as unknown, it may be a new model that Pistachio's version doesn't recognize yet. Upgrade to the latest version.

Installation and Upgrades

Stale binary after upgrade

If you upgraded but pistachio --version still shows the old version, you may have two copies installed. Check which binary is running:

which pistachio

If it shows /usr/local/bin/pistachio instead of /opt/homebrew/bin/pistachio, remove the old one:

sudo rm /usr/local/bin/pistachio

Then verify:

pistachio --version
Homebrew install fails

Make sure the DRM3 tap is added:

brew tap drm3labs/drm3

Then install:

brew install pistachio

On Apple Silicon Macs, make sure /opt/homebrew/bin is in your PATH. On Intel Macs, it should be /usr/local/bin.

Port already in use

Pistachio defaults to port 19377. If something else is using it:

pistachio config set port 8080

Or check what is using the port:

lsof -i :19377

Full Diagnostic

Run these commands and include the output if you open a support ticket:

pistachio --version
pistachio info
pistachio config show
pistachio wallet balance
pistachio session list

Also check the network status page to rule out network-wide issues:

Check Network Status

Still stuck?

Open a Support Ticket

© 2026 DRM3 Labs Corp.