# PiHole & Vaultwarden port 80 conflict

**URL:** <https://vaultwarden.discourse.group/t/pihole-vaultwarden-port-80-conflict/2833>\
**Category:** Help\
**Created:** [August 1, 2023, 3:35am UTC](https://vaultwarden.discourse.group/t/pihole-vaultwarden-port-80-conflict/2833 "2023-08-01T03:35:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kja999](https://avatars.discourse-cdn.com/v4/letter/k/eb8c5e/32.png) [@kja999](https://vaultwarden.discourse.group/u/kja999)\
**Post date:** [August 2, 2023, 8:54am UTC](https://vaultwarden.discourse.group/t/pihole-vaultwarden-port-80-conflict/2833/4 "2023-08-02T08:54:03Z")

</div>

I posted docker-compose and nginx.conf on this other thread yesterday, which might give some hints:

> [@Need help setting up my vaultwarden with duckdns](https://vaultwarden.discourse.group/t/need-help-setting-up-my-vaultwarden-with-duckdns/2504):
>
> Hello, I tried now 10 hours to get this running. my docker-compose version: '3' services: vaultwarden: image: vaultwarden/server:latest container\_name: vaultwarden restart: always volumes: - ./vw-data:/data environment: WEBSOCKET\_ENABLED: "true" # Enable WebSocket notifications. caddy: image: caddy:2 container\_name: caddy restart: always ports: - 80:80 # Needed for the ACME HTTP-01 challenge. - 443:443 volumes: …

Change the listen port there for nginx and should all work…(you can skip the duckdns parts)

---

_[View the full topic](https://vaultwarden.discourse.group/t/pihole-vaultwarden-port-80-conflict/2833)._