Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ERROR: none message must be encrypted

    Scheduled Pinned Locked Moved IPsec
    3 Posts 3 Posters 6.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F Offline
      fuzion1
      last edited by

      We have an IPsec setup with pfsense and a sonicwall.  It is becoming very unreliable, and disconnecting completely almost every night.  To fix it I have to go into pfsense and reset the connection.  I think all of this is caused by the error I am getting in my pfsense log.  It repeats this error a couple of times a second.

      Oct 7 08:38:53 racoon: [Nashville]: [] ERROR: none message must be encrypted
      Oct 7 08:38:55 racoon: [Nashville]: [] ERROR: none message must be encrypted
      Oct 7 08:38:58 racoon: [Nashville]: [] ERROR: none message must be encrypted
      Oct 7 08:39:00 racoon: [Nashville]: [] ERROR: none message must be encrypted

      Does anyone know what I can try to fix this issue?

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        That means the sonicwall is trying to send you data without encrypting it, or it's sending data on a connection that pfSense no longer considers valid.

        Check these:
        https://doc.pfsense.org/index.php/IPsec_Troubleshooting#Renegotiation_Errors

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • A Offline
          adam65535
          last edited by

          Just want to add that this can also mean the shared secret does not match.  I just ran into this error recently.  The remote end (Checkpoint) revealed in the logs that it could be a shared secret mismatch.  Sure enough it was off on one character.  The pfsense side was initiating the connection.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.