Sonaric Docs

Troubleshooting Sonaric ​

This section provides guidance on troubleshooting common issues and errors you may encounter while using Sonaric.

Installation Issues ​

WSL2 Installation ​

  • Ensure that WSL2 is installed correctly from the Microsoft Store
  • Verify that the Ubuntu-22.04 distro is created by Sonaric during installation
  • Check that the sonaricd process is running and creating a GUI on port 44004

If the installer complains about WSL2 not being installed, while it is installed, check your system language settings.

Some users have reported that the installer does not recognize WSL2 if the system language is not set to English. Please reach out to the Sonaric community on Discord for assistance.

Manual Installation on Linux ​

  • Make sure to run the one-liner to add the package registry if you need to reinstall Sonaric
  • Verify that the necessary dependencies are installed (e.g., Podman, Wireguard)
  • It's recommended to use Ubuntu 22.04 LTS. Newer versions like 23.04 or 24.04 may have issues with AppArmor settings that can interfere with Sonaric's operation.

Agent Issues ​

  • If the agent behaves unexpectedly or produces undesired results, report the issue in the Sonaric Discord server or create an issue on the GitHub repository
  • Provide detailed information about the problem, including steps to reproduce and any relevant logs or screenshots

Desktop Application Issues ​

  • The Sonaric desktop application is a Tauri application that checks the localhost port for a GUI to display
  • If the desktop application fails to start or connect to the GUI, verify that the sonaricd process is running and accessible on the expected port
  • Check the desktop application logs for any error messages or indications of the problem

VPS Installation Issues ​

  • Can't connect to the GUI or the GUI is stuck at "Connecting..." - See Accessing the GUI.
  • To access the Sonaric GUI on your VPS from your local machine, use this SSH tunnel command:
    ssh -L 127.0.0.1:44003:127.0.0.1:44003 -L 127.0.0.1:44004:127.0.0.1:44004 -L 127.0.0.1:44005:127.0.0.1:44005 -L 127.0.0.1:44006:127.0.0.1:44006 user@your-vps-ip
    Replace user@your-vps-ip with your VPS username and IP address. After establishing the tunnel, access the GUI at http://localhost:44004 in your browser.

Common Issues and Solutions ​

Node Not Working or Losing Points After Update ​

If your node stops working or isn't accumulating points after an update:

  • Wait 5-10 minutes for the node to fully initialize
  • Check sonaric ps to see if containers are running
  • If issues persist, try restarting the node with systemctl restart sonaricd
  • As a last resort, reboot your VPS or machine

Empty Results or "Not Ready" Containers in sonaric ps ​

This can happen after updates or if the node is still initializing. Wait 5-10 minutes and check again. If the issue persists, try restarting the node or rebooting your VPS.

"Command Not Found" Error ​

If you get a "command not found" error when trying to use Sonaric commands, it usually means Sonaric isn't properly installed or isn't in your system's PATH. Try reinstalling Sonaric using the official installation script.

Points Not Increasing ​

If your points are not increasing:

  • Wait at least 15-30 minutes after starting your node for the first points to appear.
  • Check if your node is running properly using sonaric ps.
  • Ensure your node meets the minimum system requirements.
  • Try restarting your node with systemctl restart sonaricd.
  • If the issue persists, reboot your VPS or machine.

High RAM Usage ​

Sonaric's RAM usage can vary, but it shouldn't consistently use more than a few hundred megabytes. If you're seeing unusually high RAM usage, monitor it over time and report persistent issues to the Sonaric team.

If you encounter an issue that is not covered here or need further assistance, please reach out to the Sonaric community on Discord or create an issue on the GitHub repository.