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
My ejabberd server sits behind an AWS ALB, which passes the x-forwarded-for http headers.
When a client connects using WebSocket, its source IP in ejabberdctl connected_users_info shows the IP address of the ALB in the subnet.
I would like that the x-forwarded-for header which is included in the http upgrade request, which is sent to initiate the WebSocket connection, will be used as the source IP of the client.
As a workaround in my test environment I used HAProxy with proxy protocol, and it showed the true client IP in ejabberd.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
My ejabberd server sits behind an AWS ALB, which passes the x-forwarded-for http headers.
When a client connects using WebSocket, its source IP in
ejabberdctl connected_users_info
shows the IP address of the ALB in the subnet.I would like that the x-forwarded-for header which is included in the http upgrade request, which is sent to initiate the WebSocket connection, will be used as the source IP of the client.
As a workaround in my test environment I used HAProxy with proxy protocol, and it showed the true client IP in ejabberd.
Thanks.
The text was updated successfully, but these errors were encountered: