Sitelet https://web.archive.org/web/20201129154901/https://github.com/vernemq/vernemq/issues/1670
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

mqtt_connect_timeout configuration is invalid #1670

Open
shenfeng07 opened this issue Nov 5, 2020 · 1 comment
Open

mqtt_connect_timeout configuration is invalid #1670

shenfeng07 opened this issue Nov 5, 2020 · 1 comment

Comments

@shenfeng07
Copy link

@shenfeng07 shenfeng07 commented Nov 5, 2020

Environment

  • VerneMQ Version: 1.11.0
  • OS: CentOS 8.0
  • Erlang/OTP version (if building from source):
  • VerneMQ configuration (vernemq.conf) or the changes from the default :
    listener.ssl.default = 0.0.0.0:8883
    listener.ssl.allowed_protocol_versions = 3,4,5
    listener.ssl.require_certificate = on
    mqtt_connect_timeout = 30000
  • Cluster size/standalone:

Expected behaviour

Set mqtt_connect_timeout to 30000 for allows more time for constrained devices to process certificates for establishing SSL connections

Actual behaviour

I tried setting mqtt_connect_timeout to 30000,but broker still close connection after 5s.

1
2

@ioolkos
Copy link
Contributor

@ioolkos ioolkos commented Nov 5, 2020

Thanks @shenfeng07
I think the mqtt_connect_timeout was only implemented half-way. (so it's possible this does not work with TLS). We should address this and have something like the handshake_timeout and ssl_handshake_timeout as RabbitMQ has.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Fixes
Low priority
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.