# Cirrus Link Distributor: Error Parsing Connect Message

**URL:** <https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660>\
**Category:** 3rd Party Modules\
**Tags:** ignition81\
**Created:** [July 24, 2024, 12:11pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660 "2024-07-24T12:11:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [January 10, 2025, 1:21pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/5 "2025-01-10T13:21:26Z")

</div>

I went through a big ordeal testing the device I was working with and led me to abandon this option. I don't remember what the exact problem was, but here are the issues I ran into as a whole.

1. The firewall was blocking the port at first
2. The certificates were not loaded correctly (I'm a CA novice). I ended up reusing the self-signed cert from Ignition's https config in Distributor.
3. The device did not support non-TLS comms so 1883 would not work.
4. The device I was using did not follow Sparkplug B spec completely.

[Ixon MQTT Evaluation: Convert data structure into a more usable format - Ignition - Inductive Automation Forum](https://forum.inductiveautomation.com/t/ixon-mqtt-evaluation-convert-data-structure-into-a-more-usable-format/95024/3)

My best guess would be to make sure you have credentials loaded to connect to Distributor.

This link should be a good place to verify your settings.  
[Getting Started: Two Ignition Architecture - MQTT Modules for Ignition 8.x - Confluence](https://docs.chariot.io/display/CLD80/Getting+Started%3A+Two+Ignition+Architecture)

---

_[View the full topic](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660)._
