File: /en/201910/rapidly-deploy-emqx-clusters-on-kubernetes-via-helm.md

replace

$ helm install my-emqx-ee emqx/emqx-ee emqxLicneseSecretName=your-license-secret-name

with

$ helm install my-emqx-ee emqx/emqx-ee --set emqxLicneseSecretName=your-license-secret-name

File: /en/202308/mqtt-performance-benchmark-testing-emqx-single-node-supports-2m-message-throughput.md

Did I misunderstand the graph/chart? Thank you

File: /zh/202208/how-to-use-mqtt-in-java.md

File: /zh/202008/use-mqtt-with-raspberry-pi.md

Greetings, I'm having problems using letsencrypt with emqx because it changed the format of the signatures (CA). Do you have any documentation to indicate?

CA X3 Expiration
https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

File: /en/201809/using-lets-encrypt-certificates-in-emq.md

File: /en/202007/enable-two-way-ssl-for-emqx.md

The 'Enable two-way SSL/TLS for EMQ X' blog example appears to never establish knowledge of the client credentials on the server. So if the server requires registered clients, this client will be rejected and the two-way TLS won't work. If the server does not require clients to be registered, then all clients will be allowed, which defeats the purpose of two-way TLS.

请问如果要给显示的数据后面添加单位，程序改如何编辑呢？
顺便捉个虫，图片显示连接的引脚是D3口，但是程序定义的是D4口。：）
File: /zh/201911/upload-sensor-data-to-mqtt-cloud-service-via-nodemcu-esp8266.md

const options = { host: 'broker.emqx.io', port: 8083, path: '/testTopic', id: 'id_' + parseInt(Math.random() * 100000), useSSL: false, };

我看到代码里面使用的是8083端口号,使用的是websocket进行了链接,我想问的是如何配置mqtt端口号进行连接呢

File: /zh/202212/how-to-cross-compile-neuron-source-code.md

你好，
有时候会遇到neuron-dashboard和neuron版本不兼容问题，能否创建一个neuron-dashboard的详细构建文档，谢谢。

File: /zh/202201/store-mqtt-messages-to-time-series-database-iotdb.md
如果是集群的话，loTDB 如何配置呢

File: /zh/201911/upload-sensor-data-to-mqtt-cloud-service-via-nodemcu-esp8266.md

File: /zh/202210/how-to-use-mqtt-in-django.md

没有查询到对应文档，esphome接入应该更简单才对，请求完善一下。

File: /zh/201909/mqtt5-new-feature-clean-start-and-session-expiry-interval.md

File: /en/202103/esp8266_mqtt_led.md
想請問一下，mqtt發送了指令"on"，但led燈不會亮

mqtt-jmeter插件现在还维护吗？
有些订阅的问题想要了解一下

File: /zh/202212/introduction-to-mqtt-qos.md

关于QoS 1的报文重复问题，我看了MQTT协议文档

造成重复的原因应该是后端对于qos1的publish包没有存任何状态，所以无法判断dup=1时，是否处理过

和package id无关吧？

File: /zh/202012/access-emqx-in-kubernetes-cluster-through-nginx-ingress-controller.md

This is useless, tarffic won't pass through ingress.

# ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
  name: emqx
spec:
  rules:
  - host: emqx.cn.iotdp.cn
    http:
      paths:
      - backend:
          serviceName: my-emqx
          servicePort: 18083
        path: /
      - backend:
          serviceName: my-emqx
          servicePort: 8083
        path: /mqtt

File: /zh/202209/advanced-features-of-mqtt-topics.md

File: /en/202203/emqx-cloud-launched-value-added-services.md

Did Professional version already include the Load Balance and NAT ?

Or it need extra price for that ?

Also: Basic deployments do not support using CNAME to bind custom domains

Can Basic deployments purchase VAS: NAT to use the CNAME feature ?

File: /zh/202010/how-to-use-mqtt-in-rust.md

File: /zh/201911/upload-sensor-data-to-mqtt-cloud-service-via-nodemcu-esp8266.md

38 client.setCallback(callback); was not declared in this scope

This line of code is redundant

File: /zh/202212/how-to-cross-compile-neuron-source-code.md

报错如下：
root@100ask:/opt/module/libjwt/build# make
[ 12%] Building C object libjwt/CMakeFiles/jwt.dir/jwt-openssl.c.o
In file included from /usr/include/openssl/bio.h:13:0,
from /opt/module/libjwt/libjwt/jwt-openssl.c:12:
/usr/include/openssl/e_os2.h:13:11: fatal error: openssl/opensslconf.h: No such file or directory

include <openssl/opensslconf.h>

File: /zh/202101/emqx-haproxy.md

问题描述

按照文档,成功部署了,HAProxy + emqx的集群. tcp和ssl连接都能正常使用.
但是碰到一个问题: 不使用集群直连时可以通过配置文件中的listener.ssl.external.peer_cert_as_username = dn 配置项, 以证书中的SubAltName做为客户端username. 但是通过HAProxy, 使用ssl连接时,username并不是 证书中的字段, 仍然是client连接时的原始username.

环境

系统为uos基于Linux version 4.19.0-desktop-amd64
emqx版本为emqx-ubuntu18.04-4.3.3-amd64.deb
HAProxy 版本 2.4.0

haproxy配置方式:

backend backend_emqx_ssl
mode tcp
balance roundrobin
server emqx_node_1 10.4.17.134:8883 check-send-proxy send-proxy-v2 check inter 10s fall 2 rise 5
server emqx_node_2 10.4.17.141:8883 check-send-proxy send-proxy-v2 check inter 10s fall 2 rise 5
frontend frontend_emqx_ssl
bind *:8005
option tcplog
mode tcp
default_backend backend_emqx_ssl
(剩余配置略)

是否需要在emqx中做额外配置?或者在HAProxy做配置,让emqx broker能正确解析证书字段?

希望尽快回复,谢谢.

File: /en/201910/rapidly-deploy-emqx-clusters-on-kubernetes-via-helm.md

This results in a successful deployment, but the pods don't run

File: /zh/202007/enable-two-way-ssl-for-emqx.md

文中开启TLS双向验证，EMQX配置文件需修改配置，校验客户端是否传证书文件。

Used together with {verify, verify_peer} by an SSL server. If set to true,

the server fails if the client does not have a certificate to send, that is,

sends an empty certificate.

Value: true | false

listener.ssl.external.fail_if_no_peer_cert = true

此配置默认注释，文中未提到此配置需为true。未开启状态下，双向验证客户端未传证书文件也可连接成功。

Hello. This blog has some claims that could do with correction: https://github.com/emqx/blog/blob/main/en/202309/aws-mqtt-managing-iot-communication-in-aws.md#emqx-cloud-vs-aws-iot-core

Some points:

• AWS IoT Core supports MQTT 5. Differences from standards: https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html#mqtt-differences
• There is no vendor lock-in with the AWS IoT Device SDKs. You can use many third party MQTT clients (https://aws.amazon.com/blogs/iot/use-aws-iot-core-mqtt-broker-with-standard-mqtt-libraries/) to connect to AWS IoT Core, and you can use AWS IoT Device SDKs with MQTT brokers other than AWS IoT Core.
• You can integrate with non AWS services. For instance using this rule action: https://docs.aws.amazon.com/iot/latest/developerguide/https-rule-action.html.
• AWS IoT Core quotas and limits help guard against "bill shock".
• Maximum concurrent client connections of 500,000 is a soft limit that can be raised.

File: /zh/202101/esp8266_mqtt_led.md
1.经测试应该在setup里面添加pinMode(LED, OUTPUT);以设置引脚才能有效控制
2.判断led开关的逻辑貌似有问题，为什么on是digitalWrite(LED, LOW);而off相反 >-<

[File: /zh/202112/how-to-use-mqtt-in-dart.md](https://www.emqx.com/zh/blog/how-to-use-mqtt-in-dart
如何在 Dart 中使用 MQTT

上面的页面是tcp的示例。能给一个dart使用websocket的示例吗？

我用mqtt_client中的示例，用websocket方式，在浏览器中使用，一直没有测试通过。贵公司能否给一个示例? 谢谢)

File: /en/202209/micro-python-mqtt-tutorial-based-on-raspberry-pi.md

I am running the 64-bit version of RasPiOS Bullseye. Installation of micropython fails with

pi@rpitest64:~ $ sudo apt install micropython -s
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package micropython
pi@rpitest64:~ $

(apt update has been run immediately prior to this.)

There does not seem to be any trace of 'micropython' in the Debian packages index for any release of Debian.

{Update: I have also tried the 32-bit version of RasPiOS Bullseye with the same (failed) result.}

File: /en/202305/a-comparison-of-iiot-protocols-mqtt-sparkplug-vs-opc-ua.md

The MQTT is shows at the Transport Layer of the OSI model. I am not sure this is accurate as it makes it look like an alternative to TCP/IP. I believe MQTT to be at the Application Layer, and requires TCP/IP as transport.

File: /zh/201903/mqtt5-message-publishing-process.md
表格格式显示错误了

File: /zh/202204/the-use-of-jmeter-mqtt-in-subscription-and-publishing-test-scenarios.md
jmeter版本：5.6.2
堆栈：
Aug 01, 2023 5:31:20 PM net.xmeter.samplers.mqtt.hivemq.HiveMQTTClient connect
INFO: Connected client: conn_e1ff2927a3824a3786
Aug 01, 2023 5:31:20 PM net.xmeter.samplers.mqtt.hivemq.HiveMQTTClient connect
INFO: Connected client: conn_a4120c4fbecb4358a6
java.lang.IllegalStateException: Current state = CODING_END, new state = FLUSHED
at java.nio.charset.CharsetDecoder.throwIllegalStateException(CharsetDecoder.java:992)
at java.nio.charset.CharsetDecoder.flush(CharsetDecoder.java:675)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:804)
at net.xmeter.samplers.mqtt.hivemq.HiveMQTTConnection.decode(HiveMQTTConnection.java:115)
at net.xmeter.samplers.mqtt.hivemq.HiveMQTTConnection.handlePublishReceived(HiveMQTTConnection.java:108)
at com.hivemq.client.internal.mqtt.mqtt3.Mqtt3AsyncClientView.lambda$callbackView$1(Mqtt3AsyncClientView.java:73)
at com.hivemq.client.internal.mqtt.MqttAsyncClient$CallbackSubscriber.onNext(MqttAsyncClient.java:227)
at com.hivemq.client.internal.mqtt.MqttAsyncClient$CallbackSubscriber.onNext(MqttAsyncClient.java:212)
at com.hivemq.client.rx.FlowableWithSingle$SingleFutureSubscriber.onNext(FlowableWithSingle.java:377)
at com.hivemq.client.internal.rx.operators.FlowableWithSingleCombine$SplitSubscriber$Default.tryOnNextActual(FlowableWithSingleCombine.java:206)
at com.hivemq.client.internal.rx.operators.FlowableWithSingleCombine$SplitSubscriber.tryOnNext(FlowableWithSingleCombine.java:171)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$ObserveOnConditionalSubscriber.runAsync(FlowableObserveOn.java:649)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run(FlowableObserveOn.java:176)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

....
....
Uncaught Exception java.lang.IllegalStateException: Current state = RESET, new state = FLUSHED in thread Thread[RxComputationThreadPool-16,5,main]. See log file for details.
Uncaught Exception java.lang.IllegalStateException: Current state = CODING_END, new state = FLUSHED in thread Thread[RxComputationThreadPool-14,5,main]. See log file for details.
Uncaught Exception java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END in thread Thread[RxComputationThreadPool-11,5,main]. See log file for details.
java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END
at java.nio.charset.CharsetDecoder.throwIllegalStateException(CharsetDecoder.java:992)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:572)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:802)
at net.xmeter.samplers.mqtt.hivemq.HiveMQTTConnection.decode(HiveMQTTConnection.java:115)
at net.xmeter.samplers.mqtt.hivemq.HiveMQTTConnection.handlePublishReceived(HiveMQTTConnection.java:108)
at com.hivemq.client.internal.mqtt.mqtt3.Mqtt3AsyncClientView.lambda$callbackView$1(Mqtt3AsyncClientView.java:73)
at com.hivemq.client.internal.mqtt.MqttAsyncClient$CallbackSubscriber.onNext(MqttAsyncClient.java:227)
at com.hivemq.client.internal.mqtt.MqttAsyncClient$CallbackSubscriber.onNext(MqttAsyncClient.java:212)
at com.hivemq.client.rx.FlowableWithSingle$SingleFutureSubscriber.onNext(FlowableWithSingle.java:377)
at com.hivemq.client.internal.rx.operators.FlowableWithSingleCombine$SplitSubscriber$Default.tryOnNextActual(FlowableWithSingleCombine.java:206)
at com.hivemq.client.internal.rx.operators.FlowableWithSingleCombine$SplitSubscriber.tryOnNext(FlowableWithSingleCombine.java:171)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$ObserveOnConditionalSubscriber.runAsync(FlowableObserveOn.java:649)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run(FlowableObserveOn.java:176)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

File: /zh/202101/emqx-haproxy.md
请问haproxy 负载均衡EMQX超过6.4W以后需要额外增加网卡来连接集群吗

File: /en/202401/mqtt-client-tools.md

https://github.com/thomasnordquist/MQTT-Explorer/commits/master/

The post says otherwise.

File: /en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md

Calling both EMQX and VerneMQ "Apache License 2.0" in the above blogpost is at best a half truth. In reality EMQX is only partly open-source (it's "opencore" strictly speaking). Basic functionality like persistence is covered under the BUSL license which by itself states: "The Business Source License is not an Open Source license." and says the work is only allowed to be used for "non-production". Not even mentioning there are parts of EMQX which are not opensource is quite frankly just disingenuous.

BTW I'm not affiliated with VerneMQ.

The example provided for connection settings differs from the example shown in the php-mqtt repository (below). The example provided here does not apply the connection settings and therefore any broker expecting a username and password will return an error 5. The emqx broker appears not to need credentials so the example here does run but the Connection Settings are not encoded. This is evident from looking at the Connect packet in Wireshark, where it shows the Connect Flags not correctly set.

$connectionSettings = (new \PhpMqtt\Client\ConnectionSettings)
->setConnectTimeout(3)
->setUseTls(true)
->setTlsSelfSignedAllowed(true);

File: /zh/202007/enable-two-way-ssl-for-emqx.md

self signed certificate in certificate chain

File: /en/202104/python-async-mqtt-client-hbmqtt.md

Please adjust the suggestion to https://github.com/Yakifo/amqtt and ensure a note exists that as of the time of this writing only Python 3.9 is supported.

File: /en/202304/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md
Thank you for sharing ...