search

rabbitmq / rabbitmq-web-stomp

Provides support for STOMP over WebSockets
Other
89 stars 26 forks source link

Unable to access stomp on server after enabling rabbitmq_web_stomp plugin #111

Closed sadjunky closed 5 years ago

sadjunky commented 5 years ago

@michaelklishin

I have enabled rabbitmq_web_stomp on the RabbitMQ server. The logs show that a port number of 15674 has been opened, but it says 404 when I try to reach it through http://hostname:15674/stomp. The Ports and Contexts section of the Management UI shows

Screen Shot 2019-04-06 at 10 10 28 AM

where http/web-stomp is shown. The Web Context shows

Screen Shot 2019-04-06 at 10 12 05 AM

This is confusing as the ports and contexts are open but yet I'm not able to access the port anywhere.

michaelklishin commented 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.

michaelklishin commented 5 years ago

I cannot suggest much as you haven't provided any example code. This plugin comes with a few example applications that you can enabled as a separate plugin, try and inspect. They use a STOMP-over-WebSockets client to access the endpoint. Regular HTTP client or Web browser won't do.

lukebakken commented 5 years ago

Please see my response.