Skip to main content
K
KerryW
Visitor II
June 15, 2026
Question

VPN Manager 7.6.7 "cannot find addr" "load vpn node failed"

  • June 15, 2026
  • 6 replies
  • 183 views

Hi

 

i have create lots of VPN definitions in the VPN Manager and assign them to Managed fortigates.  When i try and install the policy i quickly get this error.  "cannot find addr xxxx" "load vpn node x failed".   the object is there but need to be loaded on the GW.   even tryig with a policy with no VPN in the rules also fails.    Any ideas?   

    6 replies

    AEK
    SuperUser
    AEK
    SuperUser
    June 15, 2026

    Hi Kerry

    Do you mean FMG cannot create the address object on FG?

    Did you try create it manually on FG directly? Try enter the same command sequence attempted from FMG and try see why FG is rejecting it.

    AEK
      K
      KerryWAuthor
      Visitor II
      June 16, 2026

      Hi,   the firewall object is created on fortimanager.   and used on VPN manager to defines a SPOKE gateways.  but when trying to install the policy I get these errors.   in the second phase as I can’t install any policy currently.   looks as if the system trying to generate the definition from VPN managers into the fortimanger devcies database but can’t read the  fortimanger objects.

      ssangeet
      Staff
      ssangeet
      Staff
      June 15, 2026

      Are you using the external gateway in VPN manager community?
      if this is the case, then the issue you are seeing is a reported bug “1302754” - “In a VPN Manager community with external gateways, policy package installation may fail after upgrading to FortiManager 7.6.7” reference https://docs.fortinet.com/document/fortimanager/7.6.7/release-notes/454729/known-issues

      Thanks

        N
        Nomad123
        New Member
        June 16, 2026

        TLDR: I ran into the same issue, appears to be a bug

         

        Hello,

        I managed to run into the same issue. To clarify exact circumstances:
        Fortimanager version 7.6.7
        Central VPN management enabled

         

        My goal was to make a site to site tunnel with external company using the VPN Manager, I created an IPsec VPN Community with Site to Site topology. I then added Managed Gateway… so far so good. I am then able to add External Gateway, still let’s me configure everything, but now when i want to deploy the changes it fails on the same error as KerryW.
         

        cannot find addr "TEST_ADDRESS_OBJECT"load vpn node 4 failed

         

        I made sure to check that the object exists already on the FortiGate, i even created a dummy rule with that object just to make sure FortiManager does not remove it at any point. Sadly i was unable to bypass this error. I would consider this a bug. (The issue was also present in FortiManager version 8 - I know that it is not mature but i did not have any other to try it with, Fortigate still remained at 7.6.7 tho)

        D
        Dave1473
        New Member
        June 17, 2026

        Anyone aware of any work arounds for this bug?

        we have a lot of VPN’s with external gateways and can no longer push policies from Fortimanager Cloud due to this

        ssangeet
        Staff
        ssangeet
        Staff
        June 17, 2026

        Before the workaround take a backup of your FMG

        “If no changes to the VPNs are required until a fixed firmware is released then workaround is to disable the VPN Manager temporarily (edit the ADOM and disable the VPN checkbox).

        This allows other changes to be normally pushed to the FortiGates, while preserving the existing config of the already operational VPN tunnels (**note: always check the Install Preview to be on the safe side).
        Once a fixed firmware becomes available, the VPN manager can be re-enabled

        Note: With VPN Manager disabled, changes to the managed tunnels are possible via Device Manager.
        However, re-enabling VPN Manager at a later point would revert those changes.”

        D
        Dave1473
        New Member
        June 18, 2026

        Thanks

         

        We have 10 VPN’s in VPN Manager, all have external gateways.  Only 1 of these is causing this error, if i remove the external gateway from the offending VPN, then it works fine.  Do you know the conditions that triger this Bug?  I cant see what is different about this VPN to the other 9

        Terms & ConditionsAccessibility statement