when a lot seems broken at once: check convey first

if the journal dashboard at http://localhost:5015 and more than one app surface are unavailable at the same time, start by checking the journal's health. convey serves the dashboard and journal app routes, so its health is one useful first check before troubleshooting each surface separately.

check the health

from a terminal in your solstone:

journal doctor

read the health result before changing anything. if it specifically reports convey as unhealthy, restart that service:

bring convey back

journal restart-convey

then run journal doctor again and reload the dashboard at http://localhost:5015. if doctor still reports a problem, keep its exact output for the next troubleshooting step.

a note on `sol` vs. `journal`

day-to-day journal access is sol; operating the journal itself, including restarting convey, is journal. if sol restart-convey tells you the command isn't available there, that's expected: run it as journal restart-convey.

check one affected device separately

if the journal is healthy but sol still is not working on one device, inspect the registered devices and that device's status:

journal observer list
journal observer status

these commands examine device registration and status; they do not restart convey. the CLI keeps observer in the literal command name.

still stuck?

if convey will not stay up, or doctor reports something else, file a request from sol or at https://support.solstone.app/. include the exact journal doctor result after reviewing it and removing anything you do not want to send.

when a lot seems broken at once: check convey first