Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b1
Issue ID
1031144
Regression
No
Websocket over TLS with mqtt fails connection and raise unexpected exception during handshake
How to reproduce:
1. Open attached Unity project "AwsWebsocket"
2. Enter the play mode
3. Press "Connect to the endpoint"
Expected result: Websocket over TLS with mqtt connects successfully.
Actual result: Error while connecting with server pops up: "Unable to connect to the remote server" or "Invalid certificate received from server".
Reproduced with: 2018.2.0b3, 2018.1.0f2, 2017.4.2f2, 2017.2.2p4, 2017.1.3p4.
Note: User provided a Github link referencing the line where a .Net websocket breaks down in the MQTT lib:
https://github.com/chkr1011/MQTTnet/blob/master/Frameworks/MQTTnet.NetStandard/Implementations/MqttWebSocketChannel.cs#L76
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment