# Host Bitwarden behind existing nginx reverse-proxy

**URL:** <https://community.bitwarden.com/t/host-bitwarden-behind-existing-nginx-reverse-proxy/64642>\
**Category:** Password Manager\
**Tags:** server:selfhost, app:all\
**Created:** [March 18, 2024, 2:53pm UTC](https://community.bitwarden.com/t/host-bitwarden-behind-existing-nginx-reverse-proxy/64642 "2024-03-18T14:53:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JakobYooo](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@JakobYooo](https://community.bitwarden.com/u/JakobYooo)\
**Post date:** [March 18, 2024, 2:53pm UTC](https://community.bitwarden.com/t/host-bitwarden-behind-existing-nginx-reverse-proxy/64642/1 "2024-03-18T14:53:35Z")

</div>

Hi,  
i am a beginner with docker and nginx, so please keep that in mind.  
I have managed to get my nginx Docker Container running with a paperless and a portainer container which are accessible via the nginx server.  
I now want to migrate my standalone bitwarden server to this alreasy up-and-running system, but i cant seem to get bitwarden to agree not to spin up its own nginx, because i do not need it.  
I have a subdomain and the corresponding ssl certificate ready, has anybody got that kind of thing up and running?  
I would appreciate any help!

Thanks in advance and a warm greeting from cold Germany!

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [January 23, 2026, 12:56am UTC](https://community.bitwarden.com/t/host-bitwarden-behind-existing-nginx-reverse-proxy/64642/2 "2026-01-23T00:56:52Z")

</div>

Closed on January 23, 2026, 12:56am UTC


