Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

constantly and repeatedly disonnecting from emqx broker #180

Open
dkebler opened this issue Jul 27, 2019 · 5 comments
Open

constantly and repeatedly disonnecting from emqx broker #180

dkebler opened this issue Jul 27, 2019 · 5 comments

Comments

@dkebler
Copy link

dkebler commented Jul 27, 2019

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
Copy link
Owner

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
Copy link
Owner

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:
emqx/emqx#826 (comment)

@hostops
Copy link

hostops commented Mar 18, 2020

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
Copy link

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants