37 lines
1.4 KiB
Markdown
37 lines
1.4 KiB
Markdown
---
|
|
sidebar_position: 2
|
|
sidebar_label: "Limitations"
|
|
---
|
|
|
|
# Limitations and Considerations
|
|
|
|
## EasyHAProxy will not work with --network=host
|
|
|
|
:::danger Network Mode Incompatibility
|
|
The `--network=host` option **cannot** be used with the EasyHAProxy container itself due to its networking requirements.
|
|
:::
|
|
|
|
## Considerations for Multiple Replica Deployments in EasyHAProxy
|
|
|
|
:::warning Single Replica Deployment Recommended
|
|
EasyHAProxy is designed for single replica deployment.
|
|
:::
|
|
|
|
### What happens with multiple replicas?
|
|
|
|
EasyHAProxy can still operate with multiple replicas; however:
|
|
|
|
1. **Service Discovery**: Each replica will independently discover services, which may lead to temporary inconsistencies among replicas (out-of-sync for a few seconds).
|
|
|
|
2. **ACME/Certificate Issues**: Running multiple replicas creates significant problems with Let's Encrypt and other ACME certificate issuance:
|
|
- Each replica will attempt to obtain its own certificate
|
|
- ACME challenges may be directed to different replicas, causing failures
|
|
- You may quickly hit certificate issuance rate limits
|
|
- Certificate renewal may fail unpredictably
|
|
|
|
:::danger Recommendation
|
|
If you need to run multiple replicas for high availability, **do not activate ACME/Let's Encrypt**. Instead, use manually managed certificates or an external certificate management solution.
|
|
:::
|
|
|
|
----
|
|
[Open source ByJG](http://opensource.byjg.com)
|