minikube service URL does not open in the browser on Windows
Because you are using a Docker driver on windows, the terminal needs to be open to run it.Short answer
With the Docker driver on Windows, the node IP is not reachable from the host. minikube opens a tunnel for the service and prints the message that the terminal needs to be open. Keep that terminal running, use minikube service --url or minikube tunnel, and make sure Docker Desktop runs Linux containers.
Fix it fast
1Find out which cause you have
Ask Docker which kind of containers it runs, then ask minikube for a URL that works from the host.
docker info --format '{{.OSType}}' minikube service <service-name> --url2Match what you see, then jump to its fix
- 1
The URL worked once, then stopped after the terminal closed or Ctrl-CThe tunnel terminal was closed or never kept openFix - 2
EXTERNAL-IP shows <pending>A LoadBalancer service has no tunnel, so its address stays pendingFix - 3
docker info shows OSType windowsDocker Desktop is set to Windows containersFix - 4
A service on a port below 1024 does not open on WindowsA low port fails with an outdated SSH clientFix
- 1
What does the error look like?
Because you are using a Docker driver on windows, the terminal needs to be open to run it.kubectl get svc shows EXTERNAL-IP <pending>
Cause 1 of 4
The tunnel terminal was closed or never kept open
1Check
On Windows with the Docker driver, minikube service --url opens a tunnel that lives only as long as the command runs. Ctrl-C stops it and cleans up the routes.
minikube service <service-name> --url2Fix
Leave that command running in its own terminal and use the URL it prints.
# terminal 1: keep open
minikube service <service-name> --url
# terminal 2 or the browser: use the URL it printed3Verify
The page loads while the first terminal is open.
curl -I <printed-url>Confirmed by minikube.sigs.k8s.io
Cause 2 of 4
A LoadBalancer service has no tunnel, so its address stays pending
1Check
Without minikube tunnel, a LoadBalancer service never gets an external IP.
kubectl get svc2Fix
Run minikube tunnel in a separate terminal and keep it open. If it exited abruptly, clear old routes first.
minikube tunnel --cleanup
minikube tunnel3Verify
EXTERNAL-IP now holds an address; open it with the service port.
kubectl get svcConfirmed by minikube.sigs.k8s.io
Cause 3 of 4
Docker Desktop is set to Windows containers
1Check
The minikube Docker driver needs Docker Desktop's container type to be Linux.
docker info --format '{{.OSType}}'2Fix
Switch Docker Desktop to Linux containers from its tray menu, then start the cluster again.
minikube delete
minikube start --driver=docker3Verify
The command prints linux, and minikube status is Running.
docker info --format '{{.OSType}}'
minikube statusConfirmed by minikube.sigs.k8s.io
Cause 4 of 4
A low port fails with an outdated SSH client
1Check
minikube notes that on Windows with the Docker driver, ports below 1024 may fail with an outdated SSH client.
ssh -V2Fix
Install the latest OpenSSH, or expose the service on a higher port.
kubectl expose deployment <name> --type=NodePort --port=80803Verify
The service opens with the new port.
minikube service <service-name> --urlConfirmed by minikube.sigs.k8s.io
How do I stop it coming back?
- Treat the tunnel terminal as part of the setup and keep it open while you test.
- Prefer ports above 1024 for local services.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Servers
apk cannot find py-pip in an Alpine Docker image
py-pip (no such package):
On current Alpine releases there is no package called py-pip.
2 causes, each with a fixServers
ng serve runs in the container but localhost:4200 does not open
The browser cannot open localhost:4200 although ng serve is running in the container
ng serve listens on localhost by default, which inside a container is the container itself.
3 causes, each with a fixServers
Angular routes return 404 from nginx when you refresh or open a link
The home page loads, but refreshing /some/route shows an nginx 404
Angular routes like /users/42 are not files, so nginx looks for them on disk and returns 404.
3 causes, each with a fixServers
AH00558: Apache in Docker cannot reliably determine its fully qualified domain name
Set the 'ServerName' directive globally to suppress this message
AH00558 is a warning, not a crash.
2 causes, each with a fixServers
Apache in a Docker container logs AH01114 when it proxies to a backend
AH01114: HTTP: failed to make connection to backend: api
Apache's proxy worker could not open a connection to the address in ProxyPass.
5 causes, each with a fixServers
Apache logs SIGWINCH and exits on its own
the httpd container stops although nothing crashed
SIGWINCH is Apache's graceful-stop signal.
2 causes, each with a fix