Any ideas on why we get basically a 503 trying to expose the port for WebStomp with RabbitMQ? It has us perplexed. apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: field.cattle.io/creatorId: user-vnwtv field.cattle.io/ingressState: '{"c3RvbXAvcmFiYml0bXEtaGEvc3RvbXAudGV4dHJhcy5jb20vL3N0b21wLzE1Njc0":""}' field.cattle.io/publicEndpoints: '[{"addresses":["xxx.xx.xxx.x"],"port":80,"protocol":"HTTP","serviceName":"rabbitmq-ha:rabbitmq-ha-prod","ingressName":"rabbitmq-ha:stomp","hostname":"stomp.ourdomain.com","path":"/stomp","allNodes":true}]' nginx.org/websocket-services: rabbitmq-ha-prod creationTimestamp: "2020-01-29T053940Z" generation: 2 labels: cattle.io/creator: norman name: stomp namespace: rabbitmq-ha resourceVersion: "1653424" selfLink: /apis/extensions/v1beta1/namespaces/rabbitmq-ha/ingresses/stomp uid: f15178c6-3d10-4202-adbd-d9d1cc123bc5 spec: rules: - host: stomp.ourdomain.com http: paths: - backend: serviceName: rabbitmq-ha-prod servicePort: 15674 path: /stomp status: loadBalancer: ingress: - ip: xxx.xx.xxx.x It looks as though the RMQ http API used by our NodeJS code is fine as I see exchanges being created. So there is service running on that port.