I'm trying to install VerneMQ on GKE using the method suggested on VerneMQ on Kubernetes

However I get the following error:

$ curl -L https://codeload.github.com/vernemq/vmq-operator/zip/master --output repo.zip; \
> unzip -j repo.zip '*/examples/only_vernemq/*' -d only_vernemq; \
> kubectl apply -f only_vernemq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  209k    0  209k    0     0   183k      0 --:--:--  0:00:01 --:--:--  183k
Archive:  repo.zip
b06ea91fccbbc537482a8148c8eb421e3bb7bc8d
replace only_vernemq/0vernemq-operator-0namespace.yaml? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
  inflating: only_vernemq/0vernemq-operator-0namespace.yaml
  inflating: only_vernemq/0vernemq-operator-0vernemqCustomResourceDefinition.yaml
  inflating: only_vernemq/0vernemq-operator-deployment.yaml
  inflating: only_vernemq/0vernemq-operator-role.yaml
  inflating: only_vernemq/0vernemq-operator-roleBinding.yaml
  inflating: only_vernemq/0vernemq-operator-serviceAccount.yaml
  inflating: only_vernemq/vernemq-service.yaml
  inflating: only_vernemq/vernemq-serviceAccount.yaml
  inflating: only_vernemq/vernemq-vernemq.yaml
namespace/messaging created
customresourcedefinition.apiextensions.k8s.io/vernemqs.vernemq.com created
role.rbac.authorization.k8s.io/vmq-operator created
rolebinding.rbac.authorization.k8s.io/vmq-operator created
serviceaccount/vmq-operator created
service/vernemq-k8s created
serviceaccount/vernemq-k8s created
unable to recognize "only_vernemq/0vernemq-operator-deployment.yaml": no matches for kind "Deployment" in version "apps/v1beta2"
unable to recognize "only_vernemq/vernemq-vernemq.yaml": no matches for kind "VerneMQ" in version "vernemq.com/v1alpha1"

Are the docs outdated or am I doing something wrong?

At the moment, information about supported bcrypt version
currently bcrypt version 2a (prefix $2a$) is supported.
specified at the bottom of the page, but it looks as it located in the Redis section.
So, for example, If you need Mongo configuration you will read whole page, but skip Redis section, because you don't need it. And you never know that version $2b$ is not supported!
But Python implementation of the bcrypt use version $2b$ by default and for a first time it difficult to figure out why authorisation doesn't work.
I think you need to move information about supported bcrypt version to the section: Password verification and hashing methods

On https://vernemq.com/intro/mqtt-and-vernemq-for-developers/connecting_to_mqtt_and_vernemq.html#java the text says

We recommend the official Paho MQTT client library. A simple example looks like the following:

But the link https://www.eclipse.org/paho/clients/java/ is dead, should be https://www.eclipse.org/paho/index.php?page=clients/java/index.php

https://docs.vernemq.com/configuring-vernemq/the-vernemq-conf-file should lead to https://github.com/vernemq/vmq-docs/blob/1.12.3/configuration/the-vernemq-conf-file.md
it is currently empty

It looks like there is a problem on the webhook documentation.

In the documentation, it is written (https://docs.vernemq.com/plugin-development/webhookplugins):
"Note, the retry_interval is in milli-seconds. It is possible to override many more settings, see the Session Lifecycle for more information." (auth_on_register)

If I follow the link and go to the vernemq dev repo (https://github.com/vernemq/vernemq_dev/blob/master/src/auth_on_register_hook.erl), I can see the potentials modifiers under "reg_modifiers()" but I can't see the max_inflight_messages and retry_interval showed in the response example (still in webhook doc of auth_on_register https://docs.vernemq.com/plugin-development/webhookplugins)

Am I missing something ? Or does the documentation is ou of date ?

Thanks for your help !

The page at https://docs.vernemq.com/configuration/nonstandard documents the message_size_limit option, but that option is deprecated:

[warning] message_size_limit is deprecated and has no effect, use max_message_size instead

The doc stated vmq_diversity.postgres.enabled, however it should be vmq_diversity.postgres.ssl at https://docs.vernemq.com/configuration/db-auth

Hi Team,

First, I would like to like to share my humble appreciation to the vernemq team for putting together such a wonderful project and bringing enterprise grade mqtt broker to the masses.

I am currently working on a totally open source version of a vernemq admin UI app here:
https://github.com/narioinc/vmqadmin-ui ( took this up as a fun work during quarantine :) )

One of the features that I am trying to integrate is registering webhooks either runtime (vmq-admin) or persistent (allowing permanent addition to vernemq.conf)

While approaching this feature I found there to a small issue that I though the team could enhance in the vmqadmin-api.

ISSUE
When I allow the editing of the vernmq.conf file in my UI app, the conf file expects a webhook name when declaring the webhook. for e.g. vmq_webhooks.mywebhook1.hook
However when vmqadmin returns a list of webhooks, it does so without specifying the name of the webhooks in the response, and now if this GET request is used to create a page in angular/react, I don't have an idea which webhook params belongs to which weebhook name and hence operation like editing, deleting webhooks becomes ambiguous

For example
if vernemq.conf file has two webhooks like this

vmq_webhooks.mywebhook1.hook=on_publish
vmq_webhooks.mywebhook1.endpoint=http://localhost:7777/webhooks/test1
vmq_webhooks.mywebhook2.hook=on_auth_m5
vmq_webhooks.mywebhook2.endpoint=http://localhost12

then the vmqadmin REST api give back this

({
    "table": [
        {
            "hook": "on_publish",
            "endpoint": "http://localhost:7777/webhooks/test1",
            "base64payload": true,
            "response_timeout": 5000
        },
        {
            "hook": "on_publish",
            "endpoint": "http://localhost:7777/webhooks/test2",
            "base64payload": true,
            "response_timeout": 5000
        }
    ],
    "type": "table"
})

Now because I don't know which webhook name these configs are present against, other CRUD operation get affected.

I can handle this association outside of the vmqadmin API (by storing it in the sq-lite db i hold in my app) but I was thinking that can the vmq-admin API also return the webhook name as stored in the conf file if possible

On https://docs.vernemq.com/installing-vernemq/centos_and_redhat :

• vernemq-<%= latest_version() %>-1.el7.centos.x86_64.rpm looks weird

It looks like a macro blew up.

We don't need to specify versions with yum anyway - when the version we want is the latest - as it will just go get the latest from the yum repo. So, we could just say sudo yum install vernemq and let it just work.

• the yum repo URL is missing

It's customary to have a yum repo while installing via yum; otherwise it'd just be an rpm invocation. Either way, we need a URL (or instructions how to find the URL!).

(And I wouldn't recommend just pointing to bare RPMs, as that's a very old way of doing that; since yum automatically checks for updates, it's a much better way of installing RPMs and keeping them updated. If we see how many 'supply chain' security issues we have [oh, hi npm] these days, then we realize we want yum instead of just rpm)

Helm has deprecated its Charts repo (https://github.com/helm/charts) so this is now no longer correct:

https://docs.vernemq.com/guides/vernemq-on-kubernetes#deploy-vernemq-with-helm

There is only one Helm Chart on the new Helm Artifact Hub, and that's broken.
https://artifacthub.io/packages/search?ts_query_web=vernemq&sort=relevance&page=1

Recently for the latest version of vernemq, pre-compiled binaries will be available only to github sponsors. I respect that as the decision is required to generate revenue. But for community member please provide a detailed build documentation. Currently there is no build documentation on the official documentation site. On github all the documentation says is that we need Erlang/OTP and libsnappy-dev and we need to run make rel. And that's pretty much all of it.

So far with that documentation, I could only compile on a ubuntu machine. I could not compile it for alpine or debian-slim images as no list of dependencies provided.

Expected Documentation:
The documentation should mention the complete list of the dependencies with versions for different platforms. For example there is no mention on how to compile vernemq for Alpine if we want to create a custom docker image as Dockerfile on github downloads the binaries itself instead of building the code.

On page: https://docs.vernemq.com/configuration/db-auth#postgresql
The last parameter is for cockroachdb instead of postgres:

vmq_diversity.auth_postgres.enabled = on
vmq_diversity.postgres.host = 127.0.0.1
vmq_diversity.postgres.port = 5432
vmq_diversity.postgres.user = vernemq
vmq_diversity.postgres.password = vernemq
vmq_diversity.postgres.database = vernemq_db
vmq_diversity.cockroachdb.password_hash_method = crypt

Related to #1936

I configured listener.ssl.require_certificate = on and seems that this disables username/password

The docs should clarify if it's really "required", and if is it possible to keep both authentication mechanisms. May I assume without that setting client certs will be accepted? and if so, do I need to add that credential to the users file?

Finally, will be good to have instructions to troubleshoot these issues (I'm new to Verne and not sure how enable/read logs)

Maybe I missed it, but there seems to be no documentation about how to proceed if one configured the webhooks plugin but no POST requests are happening. The logs don't tell anything and the client trace only shows that the auth_on_publish hook is being called. But even the auth_on_publish does not execute any post. As we are using the docker image I guess there is not much that could be set up wrong.

Nevertheless, it seems we missed out on something during the setup of the hooks. If the documentation would show how to debug such issues users could more likely help themselves.

I have encountered an issue where the configuration file page in Vernemq Documentation is empty. When I navigate to the configuration file section in the Vernemq Documentation, instead of seeing the expected contents of the configuration file, the page appears empty.

Steps to reproduce:

1. Access the Vernemq Documentation https://docs.vernemq.com/
2. Navigate to the Vernemq Conf File. https://docs.vernemq.com/configuring-vernemq/the-vernemq-conf-file.

Expected behavior:
Upon accessing the Vernemq Conf file page, I should be able to view.
It should have to show this file content https://github.com/vernemq/vmq-docs/blob/1.12.3/configuration/the-vernemq-conf-file.md.

Actual behavior:
The Vernemq Conf File page is empty, providing no options or settings to configure.

Additional Information:
Issue still present in issue section but not resolved till now.

Currently trying to stream metrics information from localhost:8888/metrics, however i couldn't find a clear documentation on which metrics correspond to cluster overview information in the status page, e.g.: Cluster Size, Clients Online / Offline.

I am trying to implement graceful shutdown of VerneMQ container. However, I cannot find anything mentioned about:

• how to properly shutdown VerneMQ
• which steps are taken under the hood

It will be great if an example config file is provided along with documentation for beginners with vernemq. I could not find a reference config file which I can modify as per my requirements.