search

thomasnordquist / MQTT-Explorer

An all-round MQTT client that provides a structured topic overview
https://mqtt-explorer.com
Other
2.96k stars 286 forks source link

constantly and repeatedly disonnecting from emqx broker #180

Open dkebler opened 5 years ago

dkebler commented 5 years ago

First off. I have been using mqtt box for some time and it works just fine with latest emqx broker docker version.

Just saw and decided to give mqtt ex a spin. Running on a linux mint box 19+, 18.04.

The client keeps popping up the disconnected from server notification. Not all the topics are showing or are being updated.

Seems something amiss with handshaking/keep alive

connection set to mqtt protocol, valid cert off, tls off, no credentials, same as for mqttbox

Let me know how to provide you some logs

There is nothing in the dev tools console.

thomasnordquist commented 5 years ago

This may happen when you use the same MQTT client ID twice on the same broker. (or connect two MQTT Explorer instances at once).

I'll check out the compatibility with emqx in the meantime.

Thank you for the bug-report.

thomasnordquist commented 5 years ago

I had no trouble conencting to an emqx instance docker run --rm -d --name emqx -p 18083:18083 -p 1883:1883 -it emqx/emqx:latest.

However to see all the traffic you would most likely need to update your ACLs: https://github.com/emqx/emqx/issues/826#issuecomment-267917023

hostops commented 4 years ago

I have exactly same problem as above. I am using emqx. It was working before I was using x.905 certificates for authentication. Now when I try to do mTLS I get same problem as above. There is nothing in logs. If I enable validate TLS certificat (I have valid certififcate) I get image

I was also able to connect using same certificates on rabbitmq.

BTW: I can connect using MQTT.fx

ouinouin commented 3 years ago

hi, had the same issue, by changing the client ID i could get rid of the message, is the cliend ID is generated randomly ?

scottt732 commented 10 months ago

I recently switched from mosquitto to emqx and have been running into this. I think it's because of default configuration on emqx that restricts how many updates a client can receive. I have Home Assistant and a bunch of other software, some of which are using the retain flag on messages or QoS >0. MQTT Explorer seems to have a default subscription of # which can cause the client to run into the configured limits. I'm trying to figure out how to tune the configuration in emqx but may switch back to mosquitto if it's too much trouble.