|
Yes, mosquitto does (by and large) introduce itself as a client when in bridge mode, but there is still a variety of things that could be causing a failure.
Spitballing re. what you could try:
- turn on debug logging locally to see when exactly the failure occurs, for a hint as to what causing it
- turn on insecure connection (temporarily!) to verify that it’s not a CA issue (as suggested)
- play around with some of the other options (like try_private) to make sure they’re not the reason for the mess-up (the docs actually suggest setting try_private to false if a bridge connection fails)
Hope this helps!
Svet
On Sep 24, 2023, at 9:39 AM, Łukasz Przeniosło via mosquitto-dev <mosquitto-dev@xxxxxxxxxxx> wrote:
Hi Greg, thank you for the answer.
It seems obvious that you have to look in the logs of that remote system
to see what arrives and why it behaves as it does
You will also have to deal with selecting which CAs are valid. I don't
see bridge_capath in your config.
Could you refer a bit more to that? I did not need any of such when connecting directly via MQTT client. I would appreciate further feedback, thanks.
------ Original Message ------
Date 2023-09-24 15:34:27
Subject Re: [mosquitto-dev] Cannot connect to a bridge
1695506729: Connecting bridge (step 1) saupla_bridge
(mqtt85.supla.org:8883)
1695506729: Connecting bridge (step 2) saupla_bridge
(mqtt85.supla.org:8883)
1695506729: Client local.brokerSupla closed its connection.
It seems obvious that you have to look in the logs of that remote system
to see what arrives and why it behaves as it does. You can also tcpdump
on your local machine.
You will also have to deal with selecting which CAs are valid. I don't
see bridge_capath in your config.
_______________________________________________
mosquitto-dev mailing list
_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mosquitto-dev
|
