User: 하이
Assistant: 안녕하세요! 😊
User: 하이
Assistant: 안녕하세요! 😊 I'm here to help with any computer science-related questions you may have. What's on your mind? 🤔
User: 한국말 할줄 알아?
Assistant: 😊 Yes, I can understand and respond in Korean! 컴퓨터 과학 관련 질문 있으면 도와드리겠습니다! 💻
User: 너의 ai 버전은 뭐지?
Assistant: 😊 I'm a DeepSeek Coder model developed by DeepSeek Company! I'm here to assist with any computer science-related queries you may have. 💻
User: 쭉 한글로 말해줘. 내가 영어를 잘 못해.
Assistant: 걱정하지 마세요! 😊 저는 컴퓨터 과학 관련 질문에 답을 드리겠습니다. 제가 이해할 수 있는 질문이라면 무엇이든 물어보세요! 💻itra>()
User: 쭉 한글로 말해줘. 내가 영어를 잘 못해.
Assistant: 물론입니다! 😊 제가 한국어로 계속 대화할게요. 궁금한 점이나 질문이 있으면 언제든지 말씀해 주세요! 💻
User: azure container apps에서 vnet과 subnet을 설정하니 외부에서 접속이 불가능 하게 되었어. 외부 접속이 가능하게 하려면 어떻게 해야 하지?
Assistant: Azure Container Apps에서 VNet과 Subnet을 설정한 후 외부에서 접속이 불가능한 경우, 외부 접속을 가능하게 하려면 다음과 같은 단계를 고려해 볼 수 있습니다:

1. **공용 IP 주소 할당**: Azure Container Apps가 공용 IP 주소를 통해 외부에서 접근할 수 있도록 설정해야 합니다. Azure Portal에서 Container App의 설정을 확인하고, 필요한 경우 공용 IP 주소를 할당하세요.

2. **네트워크 보안 그룹(NSG) 설정**: VNet에 연결된 Subnet에 대한 네트워크 보안 그룹(NSG) 규칙을 확인하세요. 외부에서의 접근을 허용하려면 적절한 인바운드 규칙을 추가해야 합니다. 예를 들어, HTTP(포트 80) 또는 HTTPS(포트 443) 트래픽을 허용하는 규칙을 추가할 수 있습니다.

3. **프록시 또는 API Management 사용**: Azure API Management 또는 Azure Application Gateway와 같은 서비스를 사용하여 외부 요청을 Container Apps로 라우팅할 수 있습니다. 이 경우, API Management 또는 Application Gateway가 공용 IP를 가지고 외부 요청을 처리하게 됩니다.

4. **DNS 설정**: 외부에서 접근할 수 있는 도메인 이름을 설정하고, 해당 도메인이 Container App의 공용 IP 주소를 가리키도록 DNS 설정을 확인하세요.

5. **Firewall 설정**: Azure Firewall이나 다른 보안 장치가 있는 경우, 해당 장치의 설정도 확인하여 외부 트래픽이 차단되지 않도록 해야 합니다.

이 단계를 통해 외부에서 Azure Container Apps에 접근할 수 있도록 설정할 수 있습니다. 추가적인 도움이 필요하면 언제든지 말씀해 주세요!
User: DNS 설정: 외부에서 접근할 수 있는 도메인 이름을 설정하고, 해당 도메인이 Container App의 공용 IP 주소를 가리키도록 DNS 설정을 확인하세요.
Assistant: 맞습니다! DNS 설정은 Azure Container App에 외부에서 접근할 수 있도록 하는 중요한 단계입니다. 다음은 DNS 설정을 위한 기본적인 단계입니다:

1. **도메인 이름 등록**: 먼저, 사용할 도메인 이름을 등록해야 합니다. GoDaddy, Namecheap 등과 같은 도메인 등록 서비스를 통해 도메인을 구매할 수 있습니다.

2. **DNS 레코드 추가**: 도메인 등록 후, DNS 관리 페이지로 이동하여 A 레코드를 추가합니다. 이 A 레코드는 도메인 이름이 Azure Container App의 공용 IP 주소를 가리키도록 설정합니다.
   - **레코드 유형**: A
   - **호스트 이름**: www 또는 @ (루트 도메인)
   - **값**: Azure Container App의 공용 IP 주소
   - **TTL**: 기본값으로 설정하거나 원하는 값으로 설정

3. **DNS 전파 확인**: DNS 레코드를 추가한 후, 변경 사항이 전파되기까지 몇 분에서 몇 시간 정도 걸릴 수 있습니다. `nslookup` 또는 `dig` 명령어를 사용하여 도메인이 올바른 IP 주소를 가리키는지 확인할 수 있습니다.

4. **HTTPS 설정 (선택 사항)**: 보안을 위해 HTTPS를 설정하는 것이 좋습니다. Azure에서 제공하는 App Service 인증서 또는 Let's Encrypt와 같은 무료 SSL 인증서를 사용할 수 있습니다.

이 과정을 통해 외부에서 도메인 이름을 통해 Azure Container App에 접근할 수 있게 됩니다. 추가적인 질문이 있으면 언제든지 물어보세요! 😊
User: DNS 레코드 추가: 도메인 등록 후, DNS 관리 페이지로 이동하여 A 레코드를 추가합니다. 이 A 레코드는 도메인 이름이 Azure Container App의 공용 IP 주소를 가리키도록 설정합니다.
Assistant: 네, 맞습니다! DNS 레코드를 추가하는 과정은 다음과 같습니다:

1. **DNS 관리 페이지 접속**: 도메인을 등록한 서비스의 DNS 관리 페이지에 로그인합니다.

2. **A 레코드 추가**:
   - **레코드 유형**: A
   - **호스트 이름**: 도메인 이름의 서브도메인 부분을 입력합니다. 예를 들어, `www`를 입력하면 `www.yourdomain.com`이 됩니다. 루트 도메인에 대해 설정하려면 `@`를 사용할 수 있습니다.
   - **값**: Azure Container App의 공용 IP 주소를 입력합니다.
   - **TTL (Time to Live)**: 기본값으로 설정하거나 원하는 값으로 설정합니다. TTL은 DNS 레코드의 캐시 시간으로, 이 시간이 지나면 DNS 서버가 레코드를 새로 고칩니다.

3. **변경 사항 저장**: A 레코드를 추가한 후, 변경 사항을 저장합니다.

4. **DNS 전파 확인**: DNS 레코드가 올바르게 설정되었는지 확인하기 위해 `nslookup` 또는 `dig` 명령어를 사용하여 도메인이 Azure Container App의 공용 IP 주소를 가리키는지 확인합니다.

이 과정을 통해 도메인 이름을 통해 Azure Container App에 접근할 수 있게 됩니다. 추가적인 질문이나 도움이 필요하시면 언제든지 말씀해 주세요! 😊
User: 레코드 유형: A
호스트 이름: 도메인 이름의 서브도메인 부분을 입력합니다. 예를 들어, www를 입력하면 www.yourdomain.com이 됩니다. 루트 도메인에 대해 설정하려면 @를 사용할 수 있습니다.
값: Azure Container App의 공용 IP 주소를 입력합니다.
TTL (Time to Live): 기본값으로 설정하거나 원하는 값으로 설정합니다. TTL은 DNS 레코드의 캐시 시간으로, 이 시간이 지나면 DNS 서버가 레코드를 새로 고칩니다.
Assistant: 정확히 이해하셨습니다! DNS 레코드를 설정하는 과정에서 A 레코드의 구성 요소는 다음과 같습니다:

- **레코드 유형**: A
- **호스트 이름**: 도메인 이름의 서브도메인 부분을 입력합니다. 예를 들어, `www`를 입력하면 `www.yourdomain.com`이 됩니다. 루트 도메인에 대해 설정하려면 `@`를 사용할 수 있습니다.
- **값**: Azure Container App의 공용 IP 주소를 입력합니다. 이 주소는 Azure Portal에서 Container App의 설정에서 확인할 수 있습니다.
- **TTL (Time to Live)**: 기본값으로 설정하거나 원하는 값으로 설정합니다. TTL은 DNS 레코드의 캐시 시간으로, 이 시간이 지나면 DNS 서버가 레코드를 새로 고칩니다. 일반적으로 3600초(1시간) 정도로 설정하는 것이 일반적입니다.

이렇게 설정한 후, DNS 전파가 완료되면 도메인 이름을 통해 Azure Container App에 접근할 수 있게 됩니다. 추가적인 질문이나 도움이 필요하시면 언제든지 말씀해 주세요! 😊
User: 레코드 유형: A
호스트 이름: 도메인 이름의 서브도메인 부분을 입력합니다. 예를 들어, www를 입력하면 www.yourdomain.com이 됩니다. 루트 도메인에 대해 설정하려면 @를 사용할 수 있습니다.
값: Azure Container App의 공용 IP 주소를 입력합니다. 이 주소는 Azure Portal에서 Container App의 설정에서 확인할 수 있습니다.
TTL (Time to Live): 기본값으로 설정하거나 원하는 값으로 설정합니다. TTL은 DNS 레코드의 캐시 시간으로, 이 시간이 지나면 DNS 서버가 레코드를 새로 고칩니다. 일반적으로 3600초(1시간) 정도로 설정하는 것이 일반적입니다.
Assistant: 정확하게 이해하셨습니다! DNS 레코드 설정에 대한 설명이 잘 되어 있습니다. A 레코드를 통해 도메인 이름이 Azure Container App의 공용 IP 주소를 가리키도록 설정하면, 외부에서 해당 도메인을 통해 Container App에 접근할 수 있게 됩니다. 

이 외에도 궁금한 점이나 추가적인 도움이 필요하시면 언제든지 말씀해 주세요! 😊
User: Skip to main content
ContinueDocsCustomize
GitHubDiscord
SearchK
Introduction
Getting started
Install
Overview
Chat
Autocomplete
Edit
Actions
Telemetry
Troubleshooting
Customize
Troubleshooting
Troubleshooting
The Continue VS Code extension is currently in beta, and the JetBrains extension is in Alpha. If you are having trouble, please follow the steps below.
Check the logs
Try the latest pre-release
Download an older version
Resolve keyboard shortcut issues
Check FAQs for common issues
Check the logs​
To solve many problems, the first step is reading the logs to find the relevant error message. To do this, follow these steps:
VS Code​
Console logs​
info
In order to view debug logs, which contain extra information, click the dropdown at the top that says "Default levels" and select "Verbose".
cmd+shift+p (MacOS) / ctrl+shift+p (Windows)
Search for and then select "Developer: Toggle Developer Tools"
This will open the Chrome DevTools window
Select the Console tab
Read the console logs
LLM prompt logs​
If you're getting a response from the LLM that doesn't seem to make sense, you can
Open the "Output" panel (right next to the terminal)
In the dropdown, select "Continue - LLM Prompts/Completions"
View the exact prompts that were sent to the LLM and the completions recieved
JetBrains​
Open ~/.continue/logs/core.log to view the logs for the Continue plugin. The most recent logs are found at the bottom of the file.
Some JetBrains-related logs may also be found by clicking "Help" > "Show Log in Explorer/Finder".
Download the latest pre-release​
VS Code​
We are constantly making fixes and improvements to Continue, but the latest changes remain in a "pre-release" version for roughly a week so that we can test their stability. If you are experiencing issues, you can try the pre-release by going to the Continue extension page in VS Code and selecting "Switch to Pre-Release" as shown below.
JetBrains​
On JetBrains, the "pre-release" happens through their Early Access Program (EAP) channel. To download the latest EAP version, enable the EAP channel:
Open JetBrains settings (cmd/ctrl + ,) and go to "Plugins"
Click the gear icon at the top
Select "Manage Plugin Repositories..."
Add "https://plugins.jetbrains.com/plugins/eap/list" to the list
You'll now always be able to download the latest EAP version from the marketplace
Download an Older Version​
If you've tried everything, reported an error, know that a previous version was working for you, and are waiting to hear back, you can try downloading an older version of the extension.
For VS Code, All versions are hosted on the Open VSX Registry here. Once you've downloaded the extension, which will be a .vsix file, you can install it manually by following the instructions here.
You can find older versions of the JetBrains extension on their marketplace, which will walk you through installing from disk.
Keyboard shortcuts not resolving​
If your keyboard shortcuts are not resolving, you may have other commands that are taking precedence over the Continue shortcuts. You can see if this is the case, and change your shortcut mappings, in the configuration of your IDE.
VSCode keyboard shortcuts docs
IntelliJ keyboard shortcut docs
FAQs​
Networking Issues​
Configure Certificates​
If you're seeing a fetch failed error and your network requires custom certificates, you will need to configure them in config.json. In each of the objects in the "models" array, add requestOptions.caBundlePath like this:
{ "models": [ { "title": "My Model", ... "requestOptions": { "caBundlePath": "/path/to/cert.pem" } } ], ... }
You may also set requestOptions.caBundlePath to an array of paths to multiple certificates.
VS Code Proxy Settings​
If you are using VS Code and require requests to be made through a proxy, you are likely already set up through VS Code's Proxy Server Support. To double-check that this is enabled, use cmd/ctrl+, to open settings and search for "Proxy Support". Unless it is set to "off", then VS Code is responsible for making the request to the proxy.
code-server​
Continue can be used in code-server, but if you are running across an error in the logs that includes "This is likely because the editor is not running in a secure context", please see their documentation on securely exposing code-server.
I installed Continue, but don't see the sidebar window​
By default the Continue window is on the left side of VS Code, but it can be dragged to right side as well, which we recommend in our tutorial. In the situation where you have previously installed Continue and moved it to the right side, it may still be there. You can reveal Continue either by using cmd/ctrl+L or by clicking the button in the top right of VS Code to open the right sidebar.
I'm getting a 404 error from OpenAI​
If you have entered a valid API key and model, but are still getting a 404 error from OpenAI, this may be because you need to add credits to your billing account. You can do so from the billing console. If you just want to check that this is in fact the cause of the error, you can try adding $1 to your account and checking whether the error persists.
Indexing issues​
If you are having persistent errors with indexing, our recommendation is to rebuild your index from scratch. Note that for large codebases this may take some time.
This can be accomplished using the following command: Continue: Rebuild codebase index.
Android Studio - "Nothing to show" in Chat​
This can be fixed by selecting Actions > Choose Boot runtime for the IDE then selecting the latest version, and then restarting Android Studio. See this thread for details.
Still having trouble?​
You can also join our Discord community here for additional support and discussions. Alternatively, you can create a GitHub issue here, providing details of your problem, and we'll be able to help you out more quickly.
Edit this page
Previous
Telemetry
Check the logs
VS Code
JetBrains
Download the latest pre-release
VS Code
JetBrains
Download an Older Version
Keyboard shortcuts not resolving
FAQs
Networking Issues
I installed Continue, but don't see the sidebar window
I'm getting a 404 error from OpenAI
Indexing issues
Android Studio - "Nothing to show" in Chat
Still having trouble?
Extensions
VS Code
JetBrains
Community
Discord
GitHub
Follow Us
Twitter
LinkedIn
Copyright © 2024 Continue Dev, Inc.
Assistant: 죄송하지만, 제공된 텍스트는 특정한 문제 해결 절차와 관련된 내용으로 보입니다. 이와 관련하여 질문이 있으시면 구체적으로 말씀해 주시면 도움을 드리겠습니다. 예를 들어, VS Code 또는 JetBrains에서 발생하는 특정 오류에 대한 질문이 있다면, 그에 맞는 해결책을 제공해 드릴 수 있습니다. 추가적인 도움이 필요하시면 언제든지 말씀해 주세요! 😊
User: Skip to main content
ContinueDocsCustomize
GitHubDiscord
SearchK
Introduction
Getting started
Install
Overview
Chat
Autocomplete
Edit
Actions
Telemetry
Troubleshooting
Customize
Troubleshooting
Troubleshooting
The Continue VS Code extension is currently in beta, and the JetBrains extension is in Alpha. If you are having trouble, please follow the steps below.
Check the logs
Try the latest pre-release
Download an older version
Resolve keyboard shortcut issues
Check FAQs for common issues
Check the logs​
To solve many problems, the first step is reading the logs to find the relevant error message. To do this, follow these steps:
VS Code​
Console logs​
info
In order to view debug logs, which contain extra information, click the dropdown at the top that says "Default levels" and select "Verbose".
cmd+shift+p (MacOS) / ctrl+shift+p (Windows)
Search for and then select "Developer: Toggle Developer Tools"
This will open the Chrome DevTools window
Select the Console tab
Read the console logs
LLM prompt logs​
If you're getting a response from the LLM that doesn't seem to make sense, you can
Open the "Output" panel (right next to the terminal)
In the dropdown, select "Continue - LLM Prompts/Completions"
View the exact prompts that were sent to the LLM and the completions recieved
JetBrains​
Open ~/.continue/logs/core.log to view the logs for the Continue plugin. The most recent logs are found at the bottom of the file.
Some JetBrains-related logs may also be found by clicking "Help" > "Show Log in Explorer/Finder".
Download the latest pre-release​
VS Code​
We are constantly making fixes and improvements to Continue, but the latest changes remain in a "pre-release" version for roughly a week so that we can test their stability. If you are experiencing issues, you can try the pre-release by going to the Continue extension page in VS Code and selecting "Switch to Pre-Release" as shown below.
JetBrains​
On JetBrains, the "pre-release" happens through their Early Access Program (EAP) channel. To download the latest EAP version, enable the EAP channel:
Open JetBrains settings (cmd/ctrl + ,) and go to "Plugins"
Click the gear icon at the top
Select "Manage Plugin Repositories..."
Add "https://plugins.jetbrains.com/plugins/eap/list" to the list
You'll now always be able to download the latest EAP version from the marketplace
Download an Older Version​
If you've tried everything, reported an error, know that a previous version was working for you, and are waiting to hear back, you can try downloading an older version of the extension.
For VS Code, All versions are hosted on the Open VSX Registry here. Once you've downloaded the extension, which will be a .vsix file, you can install it manually by following the instructions here.
You can find older versions of the JetBrains extension on their marketplace, which will walk you through installing from disk.
Keyboard shortcuts not resolving​
If your keyboard shortcuts are not resolving, you may have other commands that are taking precedence over the Continue shortcuts. You can see if this is the case, and change your shortcut mappings, in the configuration of your IDE.
VSCode keyboard shortcuts docs
IntelliJ keyboard shortcut docs
FAQs​
Networking Issues​
Configure Certificates​
If you're seeing a fetch failed error and your network requires custom certificates, you will need to configure them in config.json. In each of the objects in the "models" array, add requestOptions.caBundlePath like this:
{ "models": [ { "title": "My Model", ... "requestOptions": { "caBundlePath": "/path/to/cert.pem" } } ], ... }
You may also set requestOptions.caBundlePath to an array of paths to multiple certificates.
VS Code Proxy Settings​
If you are using VS Code and require requests to be made through a proxy, you are likely already set up through VS Code's Proxy Server Support. To double-check that this is enabled, use cmd/ctrl+, to open settings and search for "Proxy Support". Unless it is set to "off", then VS Code is responsible for making the request to the proxy.
code-server​
Continue can be used in code-server, but if you are running across an error in the logs that includes "This is likely because the editor is not running in a secure context", please see their documentation on securely exposing code-server.
I installed Continue, but don't see the sidebar window​
By default the Continue window is on the left side of VS Code, but it can be dragged to right side as well, which we recommend in our tutorial. In the situation where you have previously installed Continue and moved it to the right side, it may still be there. You can reveal Continue either by using cmd/ctrl+L or by clicking the button in the top right of VS Code to open the right sidebar.
I'm getting a 404 error from OpenAI​
If you have entered a valid API key and model, but are still getting a 404 error from OpenAI, this may be because you need to add credits to your billing account. You can do so from the billing console. If you just want to check that this is in fact the cause of the error, you can try adding $1 to your account and checking whether the error persists.
Indexing issues​
If you are having persistent errors with indexing, our recommendation is to rebuild your index from scratch. Note that for large codebases this may take some time.
This can be accomplished using the following command: Continue: Rebuild codebase index.
Android Studio - "Nothing to show" in Chat​
This can be fixed by selecting Actions > Choose Boot runtime for the IDE then selecting the latest version, and then restarting Android Studio. See this thread for details.
Still having trouble?​
You can also join our Discord community here for additional support and discussions. Alternatively, you can create a GitHub issue here, providing details of your problem, and we'll be able to help you out more quickly.
Edit this page
Previous
Telemetry
Check the logs
VS Code
JetBrains
Download the latest pre-release
VS Code
JetBrains
Download an Older Version
Keyboard shortcuts not resolving
FAQs
Networking Issues
I installed Continue, but don't see the sidebar window
I'm getting a 404 error from OpenAI
Indexing issues
Android Studio - "Nothing to show" in Chat
Still having trouble?
Extensions
VS Code
JetBrains
Community
Discord
GitHub
Follow Us
Twitter
LinkedIn
Copyright © 2024 Continue Dev, Inc.
Assistant: 죄송하지만, 제공된 텍스트는 특정한 문제 해결 관련 내용이 아니며 혼란을 끼.Sdk합니다. 혹시 지금 처리하고자 하는 질문이나 문제를 말씀해 주시면, 저는 그에 맞는 주의한 도움을 드리겠습니다. 추가로 도움이 필요하시거나 궁금한점이 있으면 언제든지 말씀해 주세요! 😊
User: Skip to main content
ContinueDocsCustomize
GitHubDiscord
SearchK
Introduction
Getting started
Install
Overview
Chat
Autocomplete
Edit
Actions
Telemetry
Troubleshooting
Customize
Troubleshooting
Troubleshooting
The Continue VS Code extension is currently in beta, and the JetBrains extension is in Alpha. If you are having trouble, please follow the steps below.
Check the logs
Try the latest pre-release
Download an older version
Resolve keyboard shortcut issues
Check FAQs for common issues
Check the logs​
To solve many problems, the first step is reading the logs to find the relevant error message. To do this, follow these steps:
VS Code​
Console logs​
info
In order to view debug logs, which contain extra information, click the dropdown at the top that says "Default levels" and select "Verbose".
cmd+shift+p (MacOS) / ctrl+shift+p (Windows)
Search for and then select "Developer: Toggle Developer Tools"
This will open the Chrome DevTools window
Select the Console tab
Read the console logs
LLM prompt logs​
If you're getting a response from the LLM that doesn't seem to make sense, you can
Open the "Output" panel (right next to the terminal)
In the dropdown, select "Continue - LLM Prompts/Completions"
View the exact prompts that were sent to the LLM and the completions recieved
JetBrains​
Open ~/.continue/logs/core.log to view the logs for the Continue plugin. The most recent logs are found at the bottom of the file.
Some JetBrains-related logs may also be found by clicking "Help" > "Show Log in Explorer/Finder".
Download the latest pre-release​
VS Code​
We are constantly making fixes and improvements to Continue, but the latest changes remain in a "pre-release" version for roughly a week so that we can test their stability. If you are experiencing issues, you can try the pre-release by going to the Continue extension page in VS Code and selecting "Switch to Pre-Release" as shown below.
JetBrains​
On JetBrains, the "pre-release" happens through their Early Access Program (EAP) channel. To download the latest EAP version, enable the EAP channel:
Open JetBrains settings (cmd/ctrl + ,) and go to "Plugins"
Click the gear icon at the top
Select "Manage Plugin Repositories..."
Add "https://plugins.jetbrains.com/plugins/eap/list" to the list
You'll now always be able to download the latest EAP version from the marketplace
Download an Older Version​
If you've tried everything, reported an error, know that a previous version was working for you, and are waiting to hear back, you can try downloading an older version of the extension.
For VS Code, All versions are hosted on the Open VSX Registry here. Once you've downloaded the extension, which will be a .vsix file, you can install it manually by following the instructions here.
You can find older versions of the JetBrains extension on their marketplace, which will walk you through installing from disk.
Keyboard shortcuts not resolving​
If your keyboard shortcuts are not resolving, you may have other commands that are taking precedence over the Continue shortcuts. You can see if this is the case, and change your shortcut mappings, in the configuration of your IDE.
VSCode keyboard shortcuts docs
IntelliJ keyboard shortcut docs
FAQs​
Networking Issues​
Configure Certificates​
If you're seeing a fetch failed error and your network requires custom certificates, you will need to configure them in config.json. In each of the objects in the "models" array, add requestOptions.caBundlePath like this:
{ "models": [ { "title": "My Model", ... "requestOptions": { "caBundlePath": "/path/to/cert.pem" } } ], ... }
You may also set requestOptions.caBundlePath to an array of paths to multiple certificates.
VS Code Proxy Settings​
If you are using VS Code and require requests to be made through a proxy, you are likely already set up through VS Code's Proxy Server Support. To double-check that this is enabled, use cmd/ctrl+, to open settings and search for "Proxy Support". Unless it is set to "off", then VS Code is responsible for making the request to the proxy.
code-server​
Continue can be used in code-server, but if you are running across an error in the logs that includes "This is likely because the editor is not running in a secure context", please see their documentation on securely exposing code-server.
I installed Continue, but don't see the sidebar window​
By default the Continue window is on the left side of VS Code, but it can be dragged to right side as well, which we recommend in our tutorial. In the situation where you have previously installed Continue and moved it to the right side, it may still be there. You can reveal Continue either by using cmd/ctrl+L or by clicking the button in the top right of VS Code to open the right sidebar.
I'm getting a 404 error from OpenAI​
If you have entered a valid API key and model, but are still getting a 404 error from OpenAI, this may be because you need to add credits to your billing account. You can do so from the billing console. If you just want to check that this is in fact the cause of the error, you can try adding $1 to your account and checking whether the error persists.
Indexing issues​
If you are having persistent errors with indexing, our recommendation is to rebuild your index from scratch. Note that for large codebases this may take some time.
This can be accomplished using the following command: Continue: Rebuild codebase index.
Android Studio - "Nothing to show" in Chat​
This can be fixed by selecting Actions > Choose Boot runtime for the IDE then selecting the latest version, and then restarting Android Studio. See this thread for details.
Still having trouble?​
You can also join our Discord community here for additional support and discussions. Alternatively, you can create a GitHub issue here, providing details of your problem, and we'll be able to help you out more quickly.
Edit this page
Previous
Telemetry
Check the logs
VS Code
JetBrains
Download the latest pre-release
VS Code
JetBrains
Download an Older Version
Keyboard shortcuts not resolving
FAQs
Networking Issues
I installed Continue, but don't see the sidebar window
I'm getting a 404 error from OpenAI
Indexing issues
Android Studio - "Nothing to show" in Chat
Still having trouble?
Extensions
VS Code
JetBrains
Community
Discord
GitHub
Follow Us
Twitter
LinkedIn
Copyright © 2024 Continue Dev, Inc.
요약
Assistant: