Continue appears to rewrite a configured localhost API base URL to 127.0.0.1. (WSL)
I maintainer di solito rispondono entro 8 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 65/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- backend, networking
Direzione di ricerca
The report shows Continue requesting http://127.0.0.1:8080/completion even though apiBase is configured as http://localhost:8080, while http://[::1]:8080 works. Reproduce with the llama.cpp provider config given, then find where an apiBase URL is normalized, since the config is being rewritten before the request is built. Done looks like the user-supplied hostname being preserved so the request goes to localhost:8080/completion.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Before submitting your bug report
- I've tried finding an answer on the [Continue docs site](https://docs.continue.dev/)
- I'm not able to find an [open issue](https://github.com/continuedev/continue/issues?q=is%3Aopen+is%3Aissue) that reports the same bug
- I've seen the [troubleshooting guide](https://docs.continue.dev/troubleshooting) on the Continue Docs
Relevant environment info
OS: Windows with WSL2 (Ubuntu)
Continue version: V2.0.0
IDE version: VS Code 1.140.0
Model: Qwen3 14B, llama.cpp, ROCm
config:
models:
- name: Qwen3 14B (llama-rocm)
provider: llama.cpp
model: /models/Qwen3-14B-Q4_K_M.gguf
apiBase: http://localhost:8080
roles:
- chat
- edit
- apply
defaultCompletionOptions:
temperature: 0.2
maxTokens: 4096
Description
Continue appears to replace an explicitly configured localhost API base with 127.0.0.1.
My llama.cpp server is reachable through localhost and IPv6 loopback, but not through IPv4 loopback:
curl http://localhost:8080/health
# works
curl http://[::1]:8080/health
# works
curl http://127.0.0.1:8080/health
# fails
Continue is explicitly configured with:
apiBase: http://localhost:8080
However, when Continue attempts a completion, the error shows a request being made to:
http://127.0.0.1:8080/completion
This causes the request to fail with ECONNREFUSED.
The issue appears to be that Continue is replacing localhost with 127.0.0.1 instead of preserving the user-provided hostname and allowing the operating system or runtime to resolve it.
Using IPv6 explicitly works around the issue:
apiBase: http://[::1]:8080
With that configuration, Continue can connect to the llama.cpp server successfully.
Expected behavior
If apiBase is explicitly configured as:
http://localhost:8080
Continue should preserve that hostname and connect to:
http://localhost:8080/completion
It should not rewrite localhost to 127.0.0.1.
localhost and 127.0.0.1 are not always interchangeable, particularly in environments involving WSL2, IPv6, containers, and virtualized networking.
To reproduce
-
Run a llama.cpp server that is reachable through
localhostand::1, but not through127.0.0.1. -
Verify the endpoints:
curl http://localhost:8080/health
curl http://[::1]:8080/health
curl http://127.0.0.1:8080/health
- Configure Continue with:
models:
- name: Qwen3 14B (llama-rocm)
provider: llama.cpp
model: /models/Qwen3-14B-Q4_K_M.gguf
apiBase: http://localhost:8080
roles:
- chat
- edit
- apply
-
Select the model in Continue and send a chat request.
-
Observe that Continue attempts to connect to:
http://127.0.0.1:8080/completion
rather than:
http://localhost:8080/completion
- Change the configuration to:
apiBase: http://[::1]:8080
- Retry the request and observe that it succeeds.
Log output
request to http://127.0.0.1:8080/completion failed, reason: connect ECONNREFUSED 127.0.0.1:8080
- Lingua principale
- TypeScript
- Stelle
- 36.5k
- Fork
- 5.6k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di continuedev/continue
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
continuedev/continue#13486 ·
I maintainer di solito rispondono entro 8 giorni
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)Forse già presa @tang-ontheway l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
continuedev/continue#13483 ·
I maintainer di solito rispondono entro 8 giorni
-
Docs: show tool selection for a shared remote MCP endpointForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
continuedev/continue#13464 · 1 commento ·
I maintainer di solito rispondono entro 8 giorni
-
Inline code becomes unreadable in VS Code high-contrast themesForse già presa @aminesayagh l’ha presa 21 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
continuedev/continue#13424 ·
I maintainer di solito rispondono entro 8 giorni
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON valueForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
continuedev/continue#13363 ·
I maintainer di solito rispondono entro 8 giorni
Tutte le issue di continuedev/continue
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
oxc-project/tsrs#1010 ·
I maintainer di solito rispondono entro 1 giorno
-
area:infra area:storage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
THU-MAIC/OpenMAIC#2311 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
docs documentation need-triage SaaS
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement from-app needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
nightly-labs/openbot#10973 ·
I maintainer di solito rispondono entro 1 giorno
-
status/need-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
google-gemini/gemini-cli#30328 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno