Comments (5)
chkr1011
commented on June 25, 2024
1
The origin of this issue was adding support for unix sockets which exposes the base remote endpoint instead of a dedicated server and port property. In your case you must use a DnsEndPoint for the RemoteEndpoint as the WithTcpServer does. I restored the Server and Port properties because it would lead to a breaking change but unfortunately the behavior of these properties is still different. I will have a look how to restore the behavior...
from mqttnet.
chkr1011
commented on June 25, 2024
1
It was released a few seconds ago.
from mqttnet.
chkr1011
commented on June 25, 2024
I restored the old behavior. Please test build 4.3.5.1148 from MyGet and let me know if it works.
from mqttnet.
rido-min
commented on June 25, 2024
yep, it works. Thanks for the quick update!!
BTW, we will keep the other workaround of casting the RemoteEndpoint to DnsEndPoint to avoid the obsolete warning.
from mqttnet.
lukas-mertens
commented on June 25, 2024
Was this actually published in a release already? Because I don't see a 1148 release, the latest for me is a 1141 release.
from mqttnet.
Related Issues (20)
- Unable to connect with Unix Socket HOT 4
- Last Will not working? HOT 2
- [FR] Protobuf HOT 4
- PublishAsync doesn't return a result nor exception HOT 4
- Linux - when Upgrading from version 4.3.3.952 to 4.3.4.1084 the client always raises the exception «None of the discovered or specified addresses match the socket address family» HOT 7
- Restore messages per client/subscription HOT 2
- No connection could be made because the target machine actively refused it. HOT 1
- Managed MQTT client hangs when trying to disconnect using `StopAsync()` in Unity Engine HOT 5
- UWP PublishAsync forever hangs
- Event when pending ApplicationMessage was published HOT 1
- MqttClientOptionsBuilder.WithTcpServer：The “_remoteEndPoint” is missing instantiation
- Json serialized messages wont get published to the broker. HOT 3
- Connecting To localhost...Could not open connection to the host, on port 1883: Connect failed HOT 2
- The type or namespace name 'Options' does not exist in the namespace 'MQTTnet.Client' (are you missing an assembly reference?) HOT 6
- Connect async via TLS is different on Windows and Linux. HOT 3
- Issue in MQTTnet version 4.3.6.1152 HOT 1
- WebSocket connection to 'ws://127.0.0.1:10086/' failed: HOT 1
- Does this support client TLS-PSK?
- Server How to start multiple ports? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mqttnet.