Hey everyone, Our team recently upgraded to Ignition 8.3.1. Overall, our upgrade process was pretty smooth. This is our “main” Ignition gateway, and we have almost 10 other Ignition gateways that are incoming connections to this main. The connections were not really affected by the upgrade. We do …

This is an issue we're tracking internally - some "under the hood" changes caused this issue to start occurring in 8.3 and we're going to make some further changes to resolve it in the future. In the meantime, you can add a system property via the ignition.conf file that sets a larger size, in kB, …

So running into the same issue and this solution is not working for us on 8.3.2. Do you have any other suggestions? edit: Looking at the logs I can see that even though we added that to the config the error still indicates in bytes that the limit is 2048. So for some reason its not updating properl…

Did you restart after modifying ignition.conf? edit: also I would have thought this property needed to be set when launching the Designer and not in ignition.conf... but :person_shrugging:

I did and before seeing your message I instead added it as a JVM argument and that resolved the issue. I was just coming back to update my post! Thank you though for suggesting the correct solution. Edit: Just to clarify for other users that have this issue and come to this thread. What worked for …

[image] Kevin.Herron: edit: also I would have thought this property needed to be set when launching the Designer and not in ignition.conf... but :person_shrugging: It depends on which side of the handshake the too large message is coming from. For the original poster, it was happening on the …

Similar issue here with 8.3.4. Adding the property on ignition.conf and on Designer Launcher did not help. It is still stuck on 2048. Any ideas what to check? Added ignition.conf current version: #encoding=UTF-8 # Configuration files must begin with a line specifying the encoding # of the the fil…

What did you set the number to? I would try a high number to ensure you have it set high enough. I started out at the number in my post above but as we have added more that the problem tag I have had to double it since then so I just made it high enough that I don’t have to worry about it for awhile…

Problem: Still seeing this error in Gateway logs (when trying to view larger amount of string tags (JSON Payloads)) WebSocket closed with statusCode='1009', reason='Binary message too large: 2 097 974 > 2 097 152' Actions: Added this to ignition.conf wrapper.java.additional.7=-Dignition.designer…

[image] ATech: Edit: I added this to the Designer overall settings (Designer Defaults) but it did not help. Fixed it by adding the JVM argument to the specific Designer Launcher connection. It's a little confusing, but the defaults only affect new Designer entries you add to the Designer Laun…

Also just started getting this error after upgrading from 8.1 to 8.3 and the JVM args fixed it for now. some "under the hood" changes caused this issue to start occurring in 8.3 and we're going to make some further changes to resolve it in the future. Is there an estimated patch version that wou…

Binary Message Too Large in Ignition Designer

Ignition

paul-griffith July 13, 2026, 4:04pm 15

The set of changes I mentioned above are merged in to 8.3.9: