aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
author=^._.^= <maxogden@users.noreply.github.com>2016-12-20 17:01:08 -0800
committerGitHub <noreply@github.com>2016-12-20 17:01:08 -0800
commit16340f6afebb945c85de7cc815afc2f4393a4ca2 (patch)
treed45491bab7842b6f8d3c2ba50f8a9e26f1f64d14 /docs
parent092d10c5b6d36b914f024fbbe0c167bc2c284726 (diff)
downloaddat-docs-16340f6afebb945c85de7cc815afc2f4393a4ca2.tar.gz
dat-docs-16340f6afebb945c85de7cc815afc2f4393a4ca2.zip
Update faq.md
Diffstat (limited to 'docs')
-rw-r--r--docs/faq.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/faq.md b/docs/faq.md
index 790636d..f37a786 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -37,3 +37,10 @@ Our [dat.land](http://github.com/datproject/dat.land) prototype used WebRTC to t
## Do you plan to have Python or R or other third-party language integrations?
Yes. We are currently developing the serialization format (like .zip archives) called [SLEEP](/sleep) so that third-party libraries can read data without reimplementing all of hyperdrive (which is node-only).
+
+## Dat on the CLI isn't connecting, how do I debug?
+
+1. Try running `dat doctor` and following the instructions
+2. Try running your command with `DEBUG=discovery* ` in front, e.g. `DEBUG=discovery* dat sync`
+
+When reading debug output, look for `inbound connection` (means someone else successfully connected to you) or `onconnect` (you successfully connected to someone else). `discovery peer=` messages mean you found a candidate and will try to connect to them.