Skip to main content
jpapic
jpapic
Explorer
April 21, 2026
Question

Fex-extender not connecting to FortiManager Cloud.

  • April 21, 2026
  • 2 replies
  • 54 views

I have a FortiExtender (FEX) connected to my Fortinet FortiGate, with no other LAN or Internet connections, and in that scenario the device connects to FortiManager Cloud without any issue.

However, when I connect the MPLS links (used for LAN/Internet), the FortiGate is no longer shown as connected to FortiManager Cloud.

I already created:

  • A static route
  • An SD-WAN/static rule forcing FortiManager Cloud traffic to use the FEX

But the issue remains.

Tests Performed

Only FEX connected

  • ping 8.8.8.8 → Works
  • ping fortimanager.forticloud.com → Works

MPLS connected

  • ping using source interface = FEX → Fails

Question

Has anyone seen a similar issue where adding MPLS changes routing/return traffic behavior and breaks connectivity to FortiManager Cloud, even when policy routes/static routes are forcing traffic through the FEX?

 

Any suggestions would be appreciated.

    2 replies

    jiahoong112
    Staff
    jiahoong112
    Staff
    April 22, 2026

    in the FortiGate cli, could you please run this command (# get router info routing-table) and check whether you see the FEX link in the routing table or not.

    jpapic
    jpapicAuthor
    Explorer
    April 22, 2026

    Hello,

    Thanks for the tip. Routing through the FEX was working correctly, but the real issue turned out to be DNS.

    The DNS server 96.45.45.45 was not being reached through SD-WAN, so I added a static route via the FEX specifically for that DNS server.

    As soon as I applied the route, the system registered immediately.

    Thanks again

    Terms & ConditionsAccessibility statement