MqttFx | MqttFx is a mqtt v3.1.1 client using DotNetty

by linfx C# Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | MqttFx Summary

MqttFx is a C# library typically used in Internet of Things (IoT) applications. MqttFx has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

c# mqtt 3.1.1 client.

Support

Quality

Security

License

Reuse

Support

MqttFx has a low active ecosystem.

It has 76 star(s) with 37 fork(s). There are 16 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 2 have been closed. On average issues are closed in 519 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of MqttFx is current.

Quality

MqttFx has 0 bugs and 0 code smells.

Security

MqttFx has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

MqttFx code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

MqttFx is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

MqttFx releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of MqttFx

Get all kandi verified functions for this library.

MqttFx Key Features

No Key Features are available at this moment for MqttFx.

MqttFx Examples and Code Snippets

No Code Snippets are available at this moment for MqttFx.

Community Discussions

Trending Discussions on MqttFx

MQTT.fx can't connect to AWS IoT (MqttException)

TCP connection refused when hosted in IIS

Mosquitto on Home Assistant: Bridge to remote MQTT broker using CA signed server certificate

QUESTION

MQTT.fx can't connect to AWS IoT (MqttException)

Asked 2020-Oct-29 at 15:27

I am trying to follow this tutorial https://circuitdigest.com/tutorial/getting-started-with-amazon-aws-for-iot-projects

I did the all steps again and again but I can't get rid of MqttException error when click on "Connect" button in MQTT.fx.

I download the certificates from AWS IoT and keep them in C:\temp folder. I also checked log tab in MQTT.fx here you can see that below. Do you have any idea about how to solve it?

Thanks a lot!

2020-10-09 10:40:28,043 ERROR --- MqttFX ClientModel : Please verify your Settings (e.g. Broker Address, Broker Port & Client ID) and the user credentials! org.eclipse.paho.client.mqttv3.MqttException: MqttException at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:715) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:1.8.0_162] at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_162] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) ~[?:1.8.0_162] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[?:1.8.0_162] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_162] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_162] at java.lang.Thread.run(Unknown Source) [?:1.8.0_162] Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.fatalSE(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.fatalSE(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.processLoop(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.process_record(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:108) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:701) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] ... 7 more Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(Unknown Source) ~[?:1.8.0_162] at sun.security.validator.PKIXValidator.engineValidate(Unknown Source) ~[?:1.8.0_162] at sun.security.validator.Validator.validate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.processLoop(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.process_record(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:108) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:701) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] ... 7 more Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) ~[?:1.8.0_162] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source) ~[?:1.8.0_162] at java.security.cert.CertPathBuilder.build(Unknown Source) ~[?:1.8.0_162] at sun.security.validator.PKIXValidator.doBuild(Unknown Source) ~[?:1.8.0_162] at sun.security.validator.PKIXValidator.engineValidate(Unknown Source) ~[?:1.8.0_162] at sun.security.validator.Validator.validate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.processLoop(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.Handshaker.process_record(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162] at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:108) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:701) ~[org.eclipse.paho.client.mqttv3-1.2.0.jar:?] ... 7 more 2020-10-09 10:40:28,045 INFO --- ScriptsController : Clear console. 2020-10-09 10:40:28,046 ERROR --- BrokerConnectService : MqttException

...

ANSWER

Answered 2020-Oct-29 at 15:27

I solved my problem. It was about downloading the wrong certificate. You can find detailed solution here.

After you create a thing in AWS IoT, download all the 3 certificates.

If you want to get the CA certificate which is necessary for MQTT.fx you need to go here (you will see this link under the download certificates section in AWS IoT after you create your thing) and click on RSA 2048 bit key: Amazon Root CA 1 link. New tab will be open.

Copy and paste this certificate to your notepad. Name it Amazon_Root_CA_1.pem and select All File types when you are saving it.

Put all the certificates in one file. I keep them under C:\temp folder.

And finally, this is how my configuration looks like:MQTT.fx configuration

Now MQTT.fx will work hopefully :)

Source https://stackoverflow.com/questions/64276940

QUESTION

TCP connection refused when hosted in IIS

Asked 2020-Aug-07 at 05:55

I have a ASP.NET Core website that listens on 8801 port for normal HTTP request. This program also listens on the 8803 port for MQTT TCP connection.

If I run the progam with Kestrel directly on the server as below:

...

ANSWER

Answered 2020-Aug-07 at 05:55

I suggest you could try to use another way to create the MSQT server, and make sure you have open the right port to allow access.

Startup.cs:

Source https://stackoverflow.com/questions/63278216

QUESTION

Mosquitto on Home Assistant: Bridge to remote MQTT broker using CA signed server certificate

Asked 2020-Jun-18 at 17:05

How can Mosquitto (The version integrated into Home Assistant) be configured to connect as Bridge to a remote broker using only the "CA signed server certificate" option (like MQTT.fx does) with a Let's encrypt certificate?

E.g. http://mqttfx.jensd.de/ has this option in the connection settings and the connection to the broker works fine:

The configuration looks like this:

...

ANSWER

Answered 2020-Jun-18 at 17:05

Using bridge_capath /etc/ssl/certs/ instead of bridge_cafile /etc/ssl/letsencrypt.crt worked for us.

There are already a lot of pre-installed trusted certificates and the added ones (Let's Encrypt root certificate or Let's Encrypt Authority X3 certificate) in the folder.

A good link to another question explaining this (also it didn't help me), is bridge local mosquitto to cloud broker.

Source https://stackoverflow.com/questions/62451314

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install MqttFx

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: