Get help
Stuck, or something looks wrong? Ask. Dassie is early and the group around it is small, so you will usually reach the people who build it. A few lines from your node help them answer quickly.
On this page
Look here first
- Troubleshooting covers the problems people run into most, and what to do about each.
-
Check on your node explains each
line of
dassie status, which often names the problem and what to do about it. - The search box in the sidebar searches every page of these docs.
- Early days lists what Dassie does not do yet, so you know whether you hit a bug or a gap.
- Coming from a 0.2 release? A node on 0.3.0 doesn't peer with 0.2 nodes, and reads none of their phrases or databases. Set it up again with a new phrase, from a fresh database: A node from the 0.2 releases shows how, and the 0.3.0 release notes say what else changed.
Where to ask
| Where | For |
|---|---|
| Discord | Questions, setup trouble, "is this normal?", and talking about Dassie with others who run it. |
| GitHub issues | Bugs you can describe: what you did, what you expected, what happened instead. Look through the open issues first; yours may be there already. |
| Report a security issue | Anything someone could use to attack a node, a wallet or a release. Report it privately, never in an issue or on Discord. |
Everyone who answers does so in their own time, so a reply can take a while. A clear question with the lines below gets one sooner.
What to send along
On a server, run these and paste what they print.
Your node's status
$dassie status
It shows the version, the node's address and certificate, setup, the
network, its peers, ledgers and hubs, and how the last update went.
It names no secret, so its output is safe to paste as it is. If it
says you may not use the daemon's socket, run it with
sudo, or join the dassie-users group and log
in again.
The version
$dassie --version
The first line of dassie status names it too, but this
works even when the node is not running.
The log around the problem
$sudo journalctl -u dassie --since "1 hour ago" --no-pager
Change the time to cover when the problem happened. For trouble with an update, if you installed with the installer, the updater has a log of its own:
$sudo journalctl -u dassie-update --since "2 days ago" --no-pager
Read the lines before you paste them. They hold your node ID and the addresses it talks to, which are public anyway, but you may still want to trim them to the part that matters.
In the desktop app, or without a terminal
The wallet shows the same things. Settings lists the Dassie version, and Debug then Logs shows the node's recent log.
And in your own words
- how you run Dassie: the installer, NixOS or the desktop app, and on which system;
- what you did, step by step;
- what you expected, and what happened instead.
Never share these
- your recovery phrase, or a file that holds it;
-
the setup link that
dassie setup-urlprints, while setup is not done; -
an API key, a BTP token or the
code that
dassie pairprints; - anything from your node's data directory.
If one of them leaked, say so when you ask, without pasting it, and someone will help you work out what to do next.