# Cirrus Link Distributor: Error Parsing Connect Message **URL:** \ **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:** 6\ **Page:** 1
**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:** [July 24, 2024, 12:11pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/1 "2024-07-24T12:11:09Z")
Anyone seen this error before? ```python com.cirruslink.chariot.common.control.ControlPacketException: Error parsing message of type CONNECT, expected fixed header flags value (0) instead of (6) ``` I'm trying to connect to an [Ixon router](https://www.ixon.cloud/mqtt). I do not have access to the configuration on the router, the OEM is changing the settings. They showed me the configuration they used, and everything looks correct and set to Sparkplug B, port 1883, etc. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/c/7cf870af67faf4948464fee1b08b96c59af57e02.png) ---
**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:** [July 24, 2024, 12:40pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/2 "2024-07-24T12:40:24Z")
Wireshark shows missing connect packet. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/0/b0080ebc49af759249e03cf704aa0b2b13c7bc2a.png) ---
**Author:** ![mpoulsen921](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mpoulsen921](https://forum.inductiveautomation.com/u/mpoulsen921)\ **Post date:** [January 9, 2025, 9:34pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/3 "2025-01-09T21:34:25Z")
Hi, Not sure if this is still relevant but fwiw I encountered the same error message trying to connect a Shelly device to Ignition over MQTT using the MQTT Distributor module. I had to specify that the connection type should be "No SSL" instead of "TLS no validation". After selecting "No SSL" as the connection type everything worked as expected. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 9, 2025, 9:39pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/4 "2025-01-09T21:39:05Z")
> [@mpoulsen921](#): > > After selecting "No SSL" But then your (or your client's) data is going out on the internet in the clear. You should find out the underlying problem and fix it. ---
**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")
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) ---
**Author:** ![mpoulsen921](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mpoulsen921](https://forum.inductiveautomation.com/u/mpoulsen921)\ **Post date:** [January 10, 2025, 3:15pm UTC](https://forum.inductiveautomation.com/t/cirrus-link-distributor-error-parsing-connect-message/93660/6 "2025-01-10T15:15:12Z")
You are absolutely right. Shouldn't have recommended that. In my case, this is just on the local area network on an isolated network with no connection to the internet, so it is less important to have SSL on it.