# Collabora HAproxy

**URL:** <https://help.nextcloud.com/t/collabora-haproxy/93041>\
**Category:** 📄 Office\
**Tags:** reverseproxy, collabora-online\
**Created:** [September 23, 2020, 3:42pm UTC](https://help.nextcloud.com/t/collabora-haproxy/93041 "2020-09-23T15:42:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lebernd](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lebernd/32/18927_2.png) [@lebernd](https://help.nextcloud.com/u/lebernd)\
**Post date:** [October 27, 2020, 10:53am UTC](https://help.nextcloud.com/t/collabora-haproxy/93041/2 "2020-10-27T10:53:10Z")

</div>

Solved - as always: don’t just set up the 19 right places when there are 20.

So components:

- unbound (for redirecting lan to lan with external domain - not every setup will require this)
- haproxy
- code docker
- nextcloud integration
- opnsense firewall

I’m running collabora/code and nextcloud from the same debian host in dmz. But I forgot to allow the host to reach the haproxy frontend-ip on lan…

Maybe it would be possible, or even better, to use the unbound overwrite just for the nextcloud-lan and point docker-code to the haproxy frontend-ip on dmz?!

---

_[View the full topic](https://help.nextcloud.com/t/collabora-haproxy/93041)._