Skip to content

Commit

Permalink
Merge pull request #4190 from janhq/chore/update-docs-for-new-cortex-…
Browse files Browse the repository at this point in the history
…server-port

chore: update the docs for the new Cortex server port
  • Loading branch information
louis-jan authored Dec 3, 2024
2 parents c000cd5 + 4fc884b commit d9313d6
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/src/pages/docs/error-codes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ These errors relate to the local API server's functionality.
#### Error Types
| Error Code | Cause | Solution |
|------------|----------------------------------------|--------------------------------------------------------------|
| API-1 | Port 3928 is currently unavailable. | [Local API Server Guide](/docs/local-api#step-1-set-the-local-server) |
| API-1 | Port 39291 is currently unavailable. | [Local API Server Guide](/docs/local-api#step-1-set-the-local-server) |


### 8. Extensions and Integration Errors
Expand Down
10 changes: 5 additions & 5 deletions docs/src/pages/docs/troubleshooting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -368,23 +368,23 @@ When you start a chat with a model and encounter a Something's Amiss error, here
4. Confirm your V/RAM accessibility, mainly if using virtual RAM.
5. Nvidia GPU users should download [CUDA](https://developer.nvidia.com/cuda-downloads).
6. Linux users, ensure your system meets the requirements of gcc 11, g++ 11, cpp 11, or higher. Refer to this [link](#troubleshooting-nvidia-gpu) for details.
7. You might use the wrong port when you [check the app logs](#how-to-get-error-logs) and encounter the Bind address failed at 127.0.0.1:3928 error. To check the port status, try using the `netstat` command, like the following:
7. You might use the wrong port when you [check the app logs](#how-to-get-error-logs) and encounter the Bind address failed at 127.0.0.1:39291 error. To check the port status, try using the `netstat` command, like the following:

<Tabs items={['Mac', 'Windows', 'Linux']}>
<Tabs.Tab >
```bash
netstat -an | grep 3928
netstat -an | grep 39291
```
</Tabs.Tab>
<Tabs.Tab >
```bash
netstat -ano | find "3928"
tasklist /fi "PID eq 3928"
netstat -ano | find "39291"
tasklist /fi "PID eq 39291"
```
</Tabs.Tab>
<Tabs.Tab >
```bash
netstat -anpe | grep "3928"
netstat -anpe | grep "39291"
```
</Tabs.Tab>
</Tabs>
Expand Down

0 comments on commit d9313d6

Please sign in to comment.