Troubleshooting Tip: Address objects referenced to SSL VPN Portals are not pushed/installed
| Description | This article describes the troubleshooting steps that can be taken when FortiManager is not pushing objects that are referenced to the SSL VPN Portal in FortiManager. |
| Scope | FortiManager. |
| Solution | Users may encounter the following issue in FortiManager, where address objects that are referenced to an SSL VPN Portal are not pushed.
The following is the configuration in FortiManager:
Which has already been pushed to the FortiGate before:
However, when adding/referencing another address object:
The Install Preview shows nothing to be installed:
This usually means that the VPN Portal itself was unlinked from the FortiGate. To fix this, run the following command, which will link the VPN Portal to the FortiGate:
execute fmpolicy link-adom-object <adom> <category> <object_name> <device> <vdom>
In the example above, the following command was run to link the portal to the FortiGate:
execute fmpolicy link-adom-object test "vpn ssl web portal" test-portal FGT40F-1 root
Once the object has been linked, the Install Preview should show the correct configuration being pushed:
|
