diff --git a/admin_manual/installation/deployment_recommendations.rst b/admin_manual/installation/deployment_recommendations.rst
index 16ce3f63d..15a184cc5 100644
--- a/admin_manual/installation/deployment_recommendations.rst
+++ b/admin_manual/installation/deployment_recommendations.rst
@@ -414,7 +414,7 @@ Provider setup:
 * Least load to Apache servers (2-n)
 * Memcached/Redis for shared session storage (2-n)
 * Database cluster with single Master, multiple slaves and proxy to split
-  requests accordingly (2-n) - HAProxy or `MaxScale`_ are possible proxy
+  requests accordingly (2-n) - `MaxScale`_ is a possible proxy
   solutions to load balance the writes to the master and reads to the slaves
   (see "Database load balancer" below)
 * GPFS or Ceph via phprados (2-n, 3 to be safe, Ceph 10+ nodes to see speed
@@ -456,8 +456,6 @@ When Galera cluster is used as DB cluster solution, we recommend to use
 `MaxScale`_ as load balancer infront of the cluster to distribute writes to
 the master node and reads to the slaves.
 
-As alternative also `HAProxy can be used as load balancer for the DB`_.
-
 Software Considerations
 -----------------------
 
@@ -579,8 +577,6 @@ References
    http://galeracluster.com/documentation-webpages/isolationlevels.html#understanding-isolation-levels
 .. _contact the Nextcloud team:
    https://nextcloud.com/contact/
-.. _HAProxy can be used as load balancer for the DB:
-   https://severalnines.com/blog/avoiding-deadlocks-galera-set-haproxy-single-node-writes-and-multi-node-reads
 .. _MaxScale:
    https://mariadb.com/products/mariadb-maxscale
 .. _HAProxy: