It is possible to pass modifiers along with the “result”: “ok” return value of your webhook for VerneMQ.The official documentation of VerneMQ gives some examples for the syntax. changing the mountpointIt is also possible to change the mountpoint, however the client_id apparently has to be passed in as well!I have raised an issue with the [...]
The CONNECT packetThe MQTT CONNECT Control packet always contains a payload. It is the first packet, which the client must send to the server after the connection is established.It can only be sent once by the client, if a second CONNECT packet is sent, the server (broker) must process it as a protocol violation and [...]
TL;DRhttps://github.com/vernemq/vernemq/blob/master/apps/vmq_diversity/src/vmq_diversity_plugin.erlincludes a statement which will block authentication / authorization through any other channels if your Lua script returns “false”:will lead to:instead of trying other plugins, as you might have assumed!In order to avoid this problem, simply do not return anything from your Lua script, if you do not want to handle the message!DebuggingVerneMQ has a [...]
Webhooksactivate webhooks like this in your vernemq.conf.local (.local when running on docker, so that settings at bottom of the file will persist):plugins.vmq_webhooks = onvmq_webhooks.js_auth_on_register.hook = auth_on_register vmq_webhooks.js_auth_on_register.endpoint = http://container_picockpit:1200/example/pathNote that if your webhook is not accessible (econnrefused), the db based authentication will also fail … ! If you get errors like the following:jalpine_morpheus | 17:11:10.394 [...]
Besides routing and redirecting you can serve static responses with Envoy.In this case I want to serve a forbidden response (403)route_config: virtual_hosts: - name: picockpit domains: ["picockpit.local:443", "picockpit.local"] routes: - match: { prefix: "/demo" } direct_response: status: 403 body: inline_string: "Forbidden." - match: {prefix: "/"} route: {cluster: target_picockpit}It can also serve up files from [...]
Using Paho in Python with websockets and self-signed certificates for a https:// websocket connection has a couple of pitfalls, so I’m addressing this with some sample code here:import ssl import time import paho.mqtt.client as mqtt class PCPMQTTClient: def on_connect(self, client, userdata, flags, rc): self.connection_status = rc if rc == 0: self.connected_flag = True self.connection_error_flag = [...]
SituationYou edit vernemq.conf, only to find that your configuration is overwritten by VerneMQ on the next start (using the official Docker container).Specifically, the section with the listeners at the end of the file is “forced upon you”.SolutionVerneMQ is started using a script (start_vernemq). The script can be seen here:https://github.com/vernemq/docker-vernemq/blob/master/bin/vernemq.shThe important part is here:As you see, [...]
Some quick background information for anyone running into the same issues, and how to debug them.Error code 503This is the error code I am getting:Error during WebSocket handshake: Unexpected response code: 503.Set envoy logging to debugHere’s my docker-compose.yaml for envoy:version: '3.7' services: envoy: build: context: ./ dockerfile: Dockerfile container_name: penvoyage-morpheus-envoy ports: - "80:1080" - "443:1443" [...]
In my article yesterday I discussed the configuration & test of envoy for proxying websockets at length.Today I would like to add some additional information.correct syntax for websocket upgrade per routeYou can enable websocket upgrade per route. No need to add it globally:- name: envoy.http_connection_manager config: #upgrade_configs: # - upgrade_type: websocket stat_prefix: ingress_https use_remote_address: true [...]