Troubleshooting

Common issues and how to fix them.

“No module named …” errors

• Ensure you’re inside the virtualenv: source .venv/bin/activate. or whatever it is for your terminal, set.py should tell you or use uv venv
• Reinstall dependencies: pip install -r requirements.txt or uv pip install -r requirements.txt.

Port already in use (web UI)

• Change the web port in your configuration or CLI.
• Kill any existing Enclave/user/system processes using that port.

Peers not discovering each other

• Verify both instances are on the same network.
• Check firewall settings; allow the relevant ports.
• Ensure discovery plugins/transports are enabled and configured.
• Use a diffrent transports.

Plugin failures (Bluetooth, SMS)

• Confirm hardware is present and accessible.
• Check OS-level permissions (e.g., Bluetooth access).
• Review logs for plugin-specific errors.

Profile or passkey issues

• Ensure you’re using the correct passkey for the profile.
• If a profile is corrupted, you may need to delete its directory and recreate it (back up keys first if needed).

Logs and diagnostics

• Copy all the log files (or the log files for the service/profile/plugin you have issues with) and send it to support@projectenclave.dev or if it doesnt contain any private info, submit a GitHub issue

If you encounter a new issue, open a GitHub issue with:

• Enclave version / commit hash
• OS and Python version
• Steps to reproduce
• Relevant logs or screenshots
• Etc