Troubleshooting

Use these checks when RipDock cannot reach Hermes, Pairing does not complete, Agents do not appear, or chat does not respond.

Plugin Does Not Appear in Hermes

  • Confirm the plugin was copied to the Hermes plugins directory.
  • Confirm the installed folder is named ripdock.
  • Restart Hermes or rescan plugins.
  • Check Hermes logs for plugin loading errors.

Public URL Is Unreachable

  • Confirm Hermes is running locally.
  • Confirm your tunnel process is running.
  • Confirm DNS points to the tunnel.
  • Open your public URL in a browser and check for a response.

Runtime Identity Fails

Run these checks with your actual public Hermes URL.

curl https://hermes.example.com/.well-known/ripdock/runtime-identity
curl https://hermes.example.com/.well-known/ripdock/runtime-metadata

If either request fails, RipDock cannot pair yet. Fix Hermes, the plugin, or the tunnel first.

Device Stuck Waiting for Approval

  • Open the Hermes dashboard.
  • Open the RipDock plugin page.
  • Find the pending Device by fingerprint.
  • Approve the matching Device.
  • Tap Refresh Status in the App if it does not update automatically.

Fingerprint Does Not Match

Do not approve the Device. Reject the request in Hermes, cancel Pairing in RipDock, and start Pairing again.

No Agents Appear

  • Confirm the RipDock Hermes plugin is loaded.
  • Confirm Hermes has Agents configured.
  • Refresh the App or reconnect the Hermes Runtime.
  • Check Hermes logs for Agent discovery errors.

Chat Opens but No Response Appears

  • Confirm Hermes is still running.
  • Confirm the tunnel is still connected.
  • Confirm the selected Agent can respond inside Hermes.
  • Try sending a new message after refreshing the Connection.

Reset and Pair Again

  1. Remove the Hermes Connection from RipDock.
  2. Revoke or remove the old Device entry in the Hermes dashboard.
  3. Confirm your public URL still returns Runtime identity JSON.
  4. Start Pairing again from the App.