Closed Wesure6 closed 5 years ago
Thank you for your time.
Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).
We get at least a dozen of questions through various venues every single day, often light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.
Please post this to rabbitmq-users.
Thank you.
Apparently this is not covered very well in the Web MQTT docs for 3.7.8 but I think we expanded that guide for 3.7.9. You have the web_mqtt.tcp.ip
configuration key, used just like its counterparts in other listeners/protocols that are covered e.g. in Networking.
I'll make sure by the time 3.7.9 ships this will be covered for Web MQTT and Web STOMP.
only the port 1883 is listen to ipv6
how to config ? let the port 15675 listen to ipv6