-
Notifications
You must be signed in to change notification settings - Fork 50
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
Connection refused, not authorized #26
Comments
Facing the same issue!! |
me too!! |
me too too too |
http://www.lucadentella.it/en/2017/12/04/esp32-28-mqtt-e-ssl/ COPY AND PASTE IN THE ADDRESS BAR |
me too, your link can't use |
copy and paste in the address bar |
ok thank |
I use test.mosquitto.org for broker. why my connection is Connection refused, not authorized. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I tried to run the sample file on the MQTT connection, but the connection was refused, could anyone help me to understand what the problem is?
Thank you.
I (139) MQTT_SAMPLE: start the WIFI SSID:[Felipe] password:[******]
I (170) phy: phy_version: 359.0, e79c19d, Aug 31 2017, 17:06:07, 0, 0
I (171) wifi: mode : sta (30:ae:a4:0b:50:4c)
I (1136) wifi: n:8 0, o:1 0, ap:255 255, sta:8 0, prof:1
I (2123) wifi: state: init -> auth (b0)
I (2128) wifi: state: auth -> assoc (0)
I (2147) wifi: state: assoc -> run (10)
I (2185) wifi: connected with Felipe, channel 8
I (3030) event: ip: 192.168.43.107, mask: 255.255.255.0, gw: 192.168.43.1
[MQTT INFO] Starting mqtt task
[MQTT INFO] Resolve dns for domain: test.mosquitto.org
[MQTT INFO] Connecting to server 37.187.106.16:8883,45858
[MQTT INFO] Creating SSL object...
[MQTT INFO] Start SSL connect..
I (5148) wifi: pm start, type:0
[MQTT INFO] Connected!
[MQTT INFO] Connected to server test.mosquitto.org:8883
[MQTT INFO] Sending MQTT CONNECT message, type: 1, id: 0000
[MQTT INFO] Reading MQTT CONNECT response message
[MQTT WARN] Connection refused, not authorized
[MQTT INFO] Closing client socket
[MQTT INFO] Client destroyed
The text was updated successfully, but these errors were encountered: