diff options
| author | Ty Dunn <ty@tydunn.com> | 2023-08-03 16:13:18 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-08-03 16:13:18 -0700 |
| commit | 21e39505d1f2f03e370b452d4091cf29a1733572 (patch) | |
| tree | af8b135b433259a7e80f0db93293a777e7b98546 | |
| parent | 1f2bd09ea64b2ad86925b36161b8c4621a016ed7 (diff) | |
| download | sncontinue-21e39505d1f2f03e370b452d4091cf29a1733572.tar.gz sncontinue-21e39505d1f2f03e370b452d4091cf29a1733572.tar.bz2 sncontinue-21e39505d1f2f03e370b452d4091cf29a1733572.zip | |
check the server logs
| -rw-r--r-- | docs/docs/troubleshooting.md | 6 |
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: |