summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNate Sesti <sestinj@gmail.com>2023-08-03 16:36:42 -0700
committerNate Sesti <sestinj@gmail.com>2023-08-03 16:36:42 -0700
commit4eef3a5d191bcbe41c74e843088049af4124f1a2 (patch)
tree74349fd25cb4d1698c6c335e8ad01d7e7456a71c /docs
parentec4fb4d9235151901c1f7367932ecc17ab55d8e4 (diff)
parentdaafa348e5d980d28a5fed678c3545d22031fa16 (diff)
downloadsncontinue-4eef3a5d191bcbe41c74e843088049af4124f1a2.tar.gz
sncontinue-4eef3a5d191bcbe41c74e843088049af4124f1a2.tar.bz2
sncontinue-4eef3a5d191bcbe41c74e843088049af4124f1a2.zip
Merge branch 'main' of https://github.com/continuedev/continue
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/troubleshooting.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md
index f403ef7b..fcf58336 100644
--- a/docs/docs/troubleshooting.md
+++ b/docs/docs/troubleshooting.md
@@ -39,6 +39,12 @@ To get a completely fresh install of Continue, you can delete the `~/.continue`
If none of these work, you can start the server yourself as is explained here: [Running the Continue server manually](https://continue.dev/docs/how-continue-works)
+## Check the server logs
+
+1. `cmd+shift+p` (MacOS) / `ctrl+shift+p` (Windows)
+2. Search for and then select "Developer: Toggle Developer Tools"
+3. Read the `continue.log` file that has opened
+
## Check the console logs
If your Continue server is not setting up, try checking the console logs: