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

How to connect with TLS self signed certificates #80

Open
taste66 opened this issue Jun 9, 2023 · 0 comments
Open

How to connect with TLS self signed certificates #80

taste66 opened this issue Jun 9, 2023 · 0 comments

Comments

@taste66
Copy link

taste66 commented Jun 9, 2023

I want to use the MQTT-Stresser to test a MQTT broker which only supports secure links and self signed certificates.
I am using the docker but am not able to connect to the broker. Since it is a self signed certificate I added -skip-tls-verification Do I still have to provide a CA file wit this option.
I tried too with the HiveMQ broker from the example with gave the exact same result I running on Ubuntu

sudo docker run --rm inovex/mqtt-stresser -broker tcp://broker.mqttdashboard.com:8883 -skip-tls-verification -num-clients 2 -num-messages 2 -rampup-delay 1s -rampup-size 10 -global-timeout 180s -timeout 20s

Error message:
failed to unsubscribe: Not Connected
failed to unsubscribe: Not Connected

btw if I do add a CA certificate with the -ca_file option I get, independent of which certificate file I use

panic: tls: failed to find any PEM data in certificate input

goroutine 12 [running]:
main.(*Worker).Run(0xc000066580, 0x77ee20, 0xc000046420)
	/go/src/github.com/inovex/mqtt-stresser/worker.go:131 +0x1b6d
created by main.main
	/go/src/github.com/inovex/mqtt-stresser/main.go:271 +0x910

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

1 participant