Closed greffgreff closed 1 year ago
I see some mentions about proxy_protocol, if this triggers sending proxy_protocol frame at start, you also need to make ejabberd listener know about it by adding use_proxy_protocol: true in listener.
Also i see you are using 5443 port in ejabberd, and that is configured to have tls conneciton (aka it expect encrypted data, are your proxy sending tls or plain text?
I got tunnel visioned in the troubleshooting process and forgot expose port 5443 in the deployment file... Thanks anyways!
Environment
Configuration
ejabberd.yml
Ingress
Ejabberd service
Ejabberd pod logs:
Ingress logs:
Bug description
I have a kubernetes cluster deployed on an AKS instance. I am not able to connect completely to the
/ws
socket of port 5443 via an nginx ingress; while I am seeing that attempts to connect to/ws
reaches the pod as per the ingress and ejabberd logs, I am still getting a 502 response back.I have provided the configurations for the ingress with a sole endpoint to
/ws
along side the ejabberd service and the ejabberd configuration I am using and can provide more information as needed.I was unsure wether to ask this question here or on the Kuberentes github.