“Encryption not supported on this firmware” error when adding a syslog server

[Tyler_Gunn]

Hello Meraki Community,

I’m running into a puzzling issue on my network. I recently tried to add a new syslog server IP under Network-Wide >  General. Even though I’m not intending to use encryption (just standard syslog), I’m getting an error message that says:

Encryption is not supported on this firmware version.

Has anyone else seen this before? My understanding is that the firmware shouldn’t care about TLS or encrypted syslog if I’m just specifying a basic (unencrypted) syslog destination. I’ve confirmed:

• The syslog server is listening on the default UDP port 514.
• I’m not checking any boxes or toggling any settings related to secure syslog/TLS.
• The firmware on the Meraki devices is up-to-date (as far as I’m aware).

Despite all that, it refuses to accept my new syslog server entry and keeps throwing this error. Is there a specific firmware version that introduced (or removed) support for secure syslog that might be confusing here? If anyone has run into this “encryption not supported” issue or has ideas on how to resolve it, I would really appreciate the guidance.

Thanks in advance for your help!

[Mloraditch]

There is a new(ish?) option in the GUI for TLS for syslog:

I don't look at that field often, but often enough that I think I'd have seen it before. The documentation page also doesn't  mention it yet. I suspect they are in the middle of rolling this feature out and it will only work on newer models or firmware and perhaps the gui stuff isn't working right. I would call support and make them aware.

[ConnorL]

Hey @Tyler_Gunn ,

I'm able to recreate this on my personal network, can you raise a Support ticket so this can be correctly tracked?

Cheers, Connor.

[Ryan_Miles]

Seeing the same here. Also see at least one Support case opened today on it. I would suggest opening a Support case to get more evidence of it occurring. 

[RaphaelL]

Great to know that Secure Syslog is in the work !