Troubleshooting

This page lists common issues and situations that can occur during Aurono setup and strategy execution.

Most issues are not errors, but expected outcomes of configuration, safeguards, or external constraints.

Work through this page step by step before assuming something is broken.

Setup & Connectivity Issues

The Dashboard Does Not Load

Possible causes:

Aurono is not powered on
Device has not finished booting
Network connection is unavailable
You are not on the same local network

What to check:

Wait at least 2 minutes after powering on
Verify the Ethernet cable is connected
Ensure your browser device is on the same network
Try refreshing the page or another browser

The Dashboard Was Reachable Before, But Not Anymore

Possible causes:

The host’s IP address changed
Network configuration changed
The host lost power or shut down

What to check:

Power connection
Network cables and connections
Router or network changes

Aurono does not expose itself externally.

Exchange Connection Issues

Exchange Connection Test Fails

Possible causes:

Incorrect API key or secret
API permissions are insufficient
API key was revoked or expired

What to check:

API key and secret were copied correctly
Required permissions are enabled
Withdrawal permissions are disabled
API key still exists on the exchange

Re-enter credentials if in doubt.

Coinbase Connection Fails

Possible causes:

Incorrect ECDSA key formatting
Wrong portfolio selected
Key Name and Private Key swapped

What to check:

The Key Name field contains the CDP key name (starts with organizations/...)
The PEM key field contains the private key (starts with -----BEGIN EC PRIVATE KEY-----)
ECDSA is selected when generating the key on Coinbase
Primary (Standard) portfolio is used

Exchange Is Connected, But No Balances Are Shown

Possible causes:

Balance permissions are missing
Asset is held in a different portfolio or wallet
Exchange API is temporarily unavailable

What to check:

API permissions
Correct exchange selected
Exchange status page

Strategy Configuration Issues

Strategy Is Enabled, But Nothing Happens

This is the most common situation.

Possible reasons:

Buy or sell conditions were not met
Candle has not closed yet
Timeframe is long
Allocated capital is fully used

What to check:

Check the Activity feed — every evaluation is logged with the reason
Timeframe and trigger thresholds
Available allocated capital

Inactivity is normal.

Price Reached My Level, But No Trade Occurred

Explanation: Aurono evaluates only closed candles.

Intraperiod highs and lows are ignored.

What to check:

Did the candle close beyond the trigger?
Is the timeframe correct?

Buy Trigger Was Met, But No Buy Occurred

Possible causes:

Allocated capital fully used
Buy amount exceeds remaining allocation
Order size below exchange minimum
Strategy disabled at evaluation time

Aurono does not place partial or adjusted orders.

Sell Trigger Was Met, But No Sell Occurred

Possible causes:

Sell price was below average cost base
Insufficient asset balance
Order size below exchange minimum

Aurono will never sell below average cost base.

Capital & Sizing Issues

Strategy Stopped Buying

Most common cause:

Allocated capital is fully used

Aurono will not:

Borrow
Reduce order size
Exceed limits

Only Part of the Position Was Sold

This is expected behavior.

Explanation:

Sell amount limits how much is sold per trade
Partial sells are normal
Remaining assets continue to be tracked

Capital Appears Idle

Explanation: Allocated capital is a limit, not a guarantee of usage.

Aurono deploys capital only when conditions are met.

Execution & Timing Issues

Trades Feel “Late”

Explanation: Aurono waits for:

Candle close
All conditions to be satisfied

It does not react intraperiod.

Trades Feel Infrequent

Possible causes:

Long timeframe
Conservative triggers
Market conditions

This is not an error.

System & Safety Behavior

Aurono Did Nothing During a Crash or Spike

Explanation:

Intraperiod movement is ignored
Only closed candles matter
Safeguards may block execution

This is expected behavior.

Aurono Stopped Trading After Restart

Possible causes:

Strategy disabled
Exchange connection lost
Credentials revoked
License became invalid (deleted license file, hardware change, reinstall)

What to check:

Strategy status
Exchange connection test
Settings page — operating mode badge and License card

If the badge shows “shadow” with a “(license required)” hint, the system intent in the database is still live but the license isn’t validating — see License Issues below.

License Issues

Settings Shows “Shadow (License Required)” But I Haven’t Changed Anything

Possible causes:

License file was deleted or moved
Aurono was reinstalled and the license file lives outside the install
Hardware changed (Mac logic board replacement, Pi SD card swap) — the fingerprint shifted
License was revoked

What to check:

Settings → License — what does the card show?
- Not activated → the license file is gone. Re-paste your license token (you can find it in the original activation email).
- Rejected, “different device” → the fingerprint changed. Request a fresh license — see Replacing your device.
- Rejected, “invalid signature” → the file was modified or the token was pasted incorrectly. Re-paste the original.

The scheduler safely downgrades every evaluation to shadow whenever the license isn’t valid. No risk of unintended live trades while you sort this out.

License Activation Was Rejected

The License card shows an inline warning above the textarea. The message tells you exactly what went wrong:

Warning	Meaning	Fix
”This license is for a different device”	Token’s fingerprint doesn’t match this machine	Email us your current fingerprint (Settings → License → Copy) and we’ll re-issue
”This license code wasn’t recognised”	Signature mismatch — usually a copy-paste error	Re-copy the full `AUR1.…` line from the email, no extra characters
”This license code looks malformed”	Token has line breaks, spaces, or HTML formatting	Triple-click the line in your email to select cleanly, then copy
”This license code was issued for a newer version”	Aurono Start is older than the license expects	Update Aurono first (Settings → System), then re-activate

The textarea keeps the rejected token visible so you can compare it character-by-character with what’s in the email.

Exchange Row Shows “Stored API keys can’t be decrypted”

Possible causes:

The Aurono encryption key (device.key) was rotated since the credentials were saved
You reinstalled with a fresh ~/.aurono/ directory and the database still holds rows from the previous install
The device.key file was manually deleted

What to do:

Click the Re-enter keys button on the affected row. Aurono opens the Edit form pre-filled with the exchange type and label. Paste your API key and secret again — they’ll be re-encrypted with the current device.key and the row returns to normal.

The Test button is hidden for rows in this state because any call that needs the decrypted secrets would just fail.

Strategy Was Running But Stopped Evaluating

Possible causes:

Strategy was paused or archived
Exchange credentials were revoked or expired

What to check:

Strategy status on the Strategies page (Running / On hold / Archived)
Exchange connection test in Settings

When to Take Action

Consider further action if:

Dashboard does not load after power and network checks
Exchange connection consistently fails
Errors are shown in the dashboard
Configuration is correct but behavior is inconsistent over time

Otherwise, the system is likely behaving as designed.

Key Takeaway

Aurono is deterministic.

If something does not happen:

Conditions were not met
Limits were reached
Safeguards applied

This is expected behavior, not a malfunction.

Next Steps

If issues persist:

Review the Strategy Builder section
Double-check configuration
Simplify setup (one strategy, one asset)
Contact support with:
- Exchange
- Strategy settings
- Observed behavior