{"action":"created","issue":{"url":"https://api.github.com/repos/erlio/vernemq/issues/376","repository_url":"https://api.github.com/repos/erlio/vernemq","labels_url":"https://api.github.com/repos/erlio/vernemq/issues/376/labels{/name}","comments_url":"https://api.github.com/repos/erlio/vernemq/issues/376/comments","events_url":"https://api.github.com/repos/erlio/vernemq/issues/376/events","html_url":"https://github.com/erlio/vernemq/issues/376","id":226136469,"number":376,"title":"unable to receive published messages","user":{"login":"jeremylink","id":5658647,"avatar_url":"https://avatars3.githubusercontent.com/u/5658647?v=3","gravatar_id":"","url":"https://api.github.com/users/jeremylink","html_url":"https://github.com/jeremylink","followers_url":"https://api.github.com/users/jeremylink/followers","following_url":"https://api.github.com/users/jeremylink/following{/other_user}","gists_url":"https://api.github.com/users/jeremylink/gists{/gist_id}","starred_url":"https://api.github.com/users/jeremylink/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeremylink/subscriptions","organizations_url":"https://api.github.com/users/jeremylink/orgs","repos_url":"https://api.github.com/users/jeremylink/repos","events_url":"https://api.github.com/users/jeremylink/events{/privacy}","received_events_url":"https://api.github.com/users/jeremylink/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-05-03T22:48:52Z","updated_at":"2017-05-04T09:21:36Z","closed_at":null,"body":"I'm using VMQ inside the official Docker container and am having issues with receiving published messages.\r\n\r\nI've had this working in the past, so am unclear why it has stopped working on multiple environments.\r\n\r\nI'm not sure if:\r\n- there is a mystery setting in the conf file that matters\r\n- the version matters (have both the latest and version before that running)\r\n- there is something wrong with my webhook authorization response\r\n\r\nI'm running webhooks for authentication/authorization:\r\n- my auth server receives the auth_on_register and the client is able to connect\r\n- my auth server receives the auth_on_publish and auth_on_subscribe and things \"seem\" to work\r\n- none of the published messages are received by my subscriber\r\n\r\nThese are samples of the messages my auth server sends back to the broker:\r\n**auth_on_register** response:\r\n {\"result\":\"ok\",\"modifiers\":{\"mountpoint\":\"newmountpoint\",\"client_id\":\"1391f03a529f46c386aa09139698da1e\",\"clean_session\":true,\"max_message_size\":65535,\"max_message_rate\":100,\"max_inflight_messages\":100,\"retry_interval\":100,\"upgrade_qos\":false}}\r\n-> this works fine, this also logs a line in the broker log file\r\n**auth_on_subscribe** response:\r\n{\"result\":\"ok\",\"modifiers\":{\"topics\":[{\"topic\":\"foo/bar/#\",\"qos\":1}],\"payload\":\"rewritten payload\",\"retain\":true,\"reg_view\":\"reg_view\",\"mountpoint\":\"newmountpoint\"}}\r\n**auth_on_publish** response:\r\n{\"result\":\"ok\",\"modifiers\":{\"topic\":\"foo/bar/blah\",\"qos\":1,\"payload\":\"rewritten payload\",\"retain\":true,\"reg_view\":\"reg_view\",\"mountpoint\":\"newmountpoint\"}}\r\n\r\nPart of my concern is that there is no documentation on what the response messages should look like.\r\nWhich fields are required and what do they do.\r\nI've tried various values for the response field to no avail.\r\n\r\nThese are some of the settings I have in my conf file:\r\nallow_anonymous = off\r\nplugins.vmq_acl = off\r\nplugins.vmq_webhooks = on\r\n\r\nvmq_webhooks.webhook_auth_on_register.hook = auth_on_register\r\nvmq_webhooks.webhook_auth_on_register.endpoint = http://127.0.0.1:1884/app/micro-service/\r\nvmq_webhooks.webhook_auth_on_publish.hook = auth_on_publish\r\nvmq_webhooks.webhook_auth_on_publish.endpoint = http://127.0.0.1:1884/app/micro-service/\r\nvmq_webhooks.webhook_auth_on_subscribe.hook = auth_on_subscribe\r\nvmq_webhooks.webhook_auth_on_subscribe.endpoint = http://127.0.0.1:1884/app/micro-service/\r\n\r\nIn some instances I set these in the file. In other cases I pass them as environment variables to the container at startup:\r\n########## Start ##########\r\nvmq_webhooks.webhook_auth_on_publish.hook=auth_on_publish\r\nplugins.vmq_webhooks=on\r\nvmq_webhooks.webhook_auth_on_register.hook=auth_on_register\r\nvmq_webhooks.webhook_auth_on_subscribe.hook=auth_on_subscribe\r\nvmq_webhooks.webhook_auth_on_register.endpoint=http://blah.com:1884/app/micro-service\r\nvmq_webhooks.webhook_wakeup.hook=on_client_wakeup\r\nvmq_webhooks.webhook_auth_on_subscribe.endpoint=http://blah.com:1884/app/micro-service\r\nplugins.vmq_acl=off\r\nplugins.vmq_passwd=off\r\nlog.console.level=debug\r\nvmq_webhooks.webhook_wakeup.endpoint=http://blah.com:1884/app/micro-service\r\nallow_anonymous=off\r\nvmq_webhooks.webhook_auth_on_publish.endpoint=http://blah.com:1884/app/micro-service\r\nerlang.distribution.port_range.minimum = 9100\r\nerlang.distribution.port_range.maximum = 9109\r\nlistener.tcp.default = 172.17.0.2:1883\r\nlistener.ws.default = 172.17.0.2:8080\r\nlistener.vmq.clustering = 172.17.0.2:44053\r\nlistener.http.metrics = 172.17.0.2:8888\r\n########## End ##########\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/erlio/vernemq/issues/comments/299135654","html_url":"https://github.com/erlio/vernemq/issues/376#issuecomment-299135654","issue_url":"https://api.github.com/repos/erlio/vernemq/issues/376","id":299135654,"user":{"login":"larshesel","id":679187,"avatar_url":"https://avatars0.githubusercontent.com/u/679187?v=3","gravatar_id":"","url":"https://api.github.com/users/larshesel","html_url":"https://github.com/larshesel","followers_url":"https://api.github.com/users/larshesel/followers","following_url":"https://api.github.com/users/larshesel/following{/other_user}","gists_url":"https://api.github.com/users/larshesel/gists{/gist_id}","starred_url":"https://api.github.com/users/larshesel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/larshesel/subscriptions","organizations_url":"https://api.github.com/users/larshesel/orgs","repos_url":"https://api.github.com/users/larshesel/repos","events_url":"https://api.github.com/users/larshesel/events{/privacy}","received_events_url":"https://api.github.com/users/larshesel/received_events","type":"User","site_admin":false},"created_at":"2017-05-04T09:21:36Z","updated_at":"2017-05-04T09:21:36Z","body":"Hi @jeremylink could I get you to do a `vmq-admin trace client client-id=<the client id>`? That would show what happens internally in VerneMQ for that client session. Maybe that can reveal the problem."}}
{"actor":{"display_login":"larshesel"}}