You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my AWS EC2 instances the apache logs get constantly filled with errors from the ProxyProtocol module because the ELB health checks do not send a ProxyProtocol header with their checks.
ProxyProtocol: no valid header found
Can this log entry be turned into a option so I do not have to turn off all errors? Or possibly point me in the direction to disable them with the current version?
The text was updated successfully, but these errors were encountered:
The cleaner way to solve this, IMO, is to have Apache listen on two ports, one with ProxyProtocol enabled, and one without; then configure the ELB to forward requests to the port with ProxyProtocol enabled, but to run the health checks against the other port. Not only does this avoid noise in the log, but it means that the ELB can actually do a proper health check (otherwise the connection just gets aborted, severely limiting the effectiveness of the health check).
Btw., see #2 (comment) for a skeleton of how to do this setup.
On my AWS EC2 instances the apache logs get constantly filled with errors from the ProxyProtocol module because the ELB health checks do not send a ProxyProtocol header with their checks.
Can this log entry be turned into a option so I do not have to turn off all errors? Or possibly point me in the direction to disable them with the current version?
The text was updated successfully, but these errors were encountered: