Hello, I have a mqtt-integration within my application and am running paho mqtt written in golang to work with the received data.
It works perfectly fine on port 1883 without tls with the client configuration being straight forward.
But that was for testing, and I want to use tls so I changed the port to 8883 and added a tls.config to my dialoptions, just as any tutorial on it does. Weirdly enough it doesnt really matter what I change inside my config, the result I capture over Wireshark scoping the ip of the broker is the same.
The program starts with a successful tls-handshake with the port 443 and immediately connects to the port 8883, also successfully. In the 1883 example a Mqtt-Connect packet follows. In the 8883 example Wireshark interprets it as a ssl-packet. The broker acknowledges it and the connection comes to a keep-alive-freeze. A mqtt connect never occurs nor an error I could look up.
I tried all I could think of without any luck and my network expertise is mediocre.
Does anyone have any spontaneous ideas, knows of this. Or differently, how does it look from the server side if anyone has more insight on this.