You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: content/en/getting-started/faq.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -259,6 +259,32 @@ volumes:
259
259
260
260
For more details visit [Docker WSL documentation](https://docs.docker.com/desktop/wsl), [Docker WSL best practices](https://docs.docker.com/desktop/wsl/best-practices) and [Docker Volumes documentation](https://docs.docker.com/storage/volumes/).
261
261
262
+
### Why is `localhost.localstack.cloud` not resolving on Windows with WSL, and how do I fix it?
263
+
264
+
We’ve seen multiple reports where requests to `localhost.localstack.cloud` fail specifically when running on **Windows with WSL (Windows Subsystem for Linux)**.
265
+
In this scenario, tools like `curl` and LocalStack Web Application cannot connect to LocalStack container using the domain `localhost.localstack.cloud`.
266
+
267
+
This is a DNS resolution issue — the system doesn’t know that `localhost.localstack.cloud` should resolve to `127.0.0.1`.
268
+
Follow these steps to fix the issue:
269
+
270
+
1. **Update WSL DNS mapping:** Edit `/etc/hosts` in your WSL environment to include this line:
271
+
272
+
```text
273
+
127.0.0.1 localhost localhost.localstack.cloud
274
+
```
275
+
276
+
This allows tools like `curl` in WSL to resolve the domain properly.
277
+
278
+
2. **Update Windows DNS mapping:** Edit `C:\Windows\System32\drivers\etc\hosts` (as Administrator) and add the same line:
279
+
280
+
```text
281
+
127.0.0.1 localhost localhost.localstack.cloud
282
+
```
283
+
284
+
After updating, reboot your system or run `ipconfig /flushdns` to clear the DNS cache.
285
+
286
+
Once both changes are in place, the domain should resolve correctly for both WSL and Windows apps.
287
+
262
288
## LocalStack Platform FAQs
263
289
264
290
### Where can I check the status of LocalStack's services?
0 commit comments