# How to access Vaultwarden docker in local LAN

**URL:** <https://vaultwarden.discourse.group/t/how-to-access-vaultwarden-docker-in-local-lan/2258>\
**Category:** Help\
**Created:** [January 19, 2023, 2:03am UTC](https://vaultwarden.discourse.group/t/how-to-access-vaultwarden-docker-in-local-lan/2258 "2023-01-19T02:03:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [January 25, 2023, 4:58am UTC](https://vaultwarden.discourse.group/t/how-to-access-vaultwarden-docker-in-local-lan/2258/2 "2023-01-25T04:58:02Z")

</div>

The `curl` command appears to be run inside [WSL2](https://vaultwarden.discourse.group/t/vaultwarden-started-up-but-could-not-connect/2265) so it’s in a different network space than your ubuntu. I think windows runs a separate virtual machine for the linux subsystem. See [Unable to access my first container (on 172.17.0.2) - General Discussions - Docker Community Forums](https://forums.docker.com/t/unable-to-access-my-first-container-on-172-17-0-2/54106)

Does it work via your `DOMAIN`?

---

_[View the full topic](https://vaultwarden.discourse.group/t/how-to-access-vaultwarden-docker-in-local-lan/2258)._