Solved

Hi all, I'm having trouble getting 2 fortigate firewalls to connect via VPN, it looks like the phase1 is up but the phase2 never gets triggered. Even if I execute a ping between the two sides it never comes up. I've attached a screenshot of the VPN settings at both ends as well as the static routes and the firewall rules that I've got configured. I've tried running the Fortigate to Fortigate IPSEC wizard and I get the same result. I currently have NAT disabled at both ends but I've tried it with it enabled and enabled/disabled at both ends. I've checked and the preshared keys are the same and they're both using AES256-SHA256 DH14 on both the phase1 and phase2s I'm really confused, can anyone offer any advice?  

On MacOS 15 (FortiClient version 7.2.6), at the MacOS login screen a message appears prompting for credentials.  The message states: FortiClientAgentYou are making changes to your Certificate Trust Settings.Enter the name and password of a user in the "(null)" group to allow this. No matter what credentials are entered, it won't accept them. I've opened a case with support, to no avail so far.They referred me to this article (for an older version of FortiClient), and I added all the services it mentions that need full disk access and checked the other settings:https://docs.fortinet.com/document/forticlient/7.0.9/macos-release-notes/223986 I would investigate downgrading to see if that helps, but we want to be on the latest release so that we are up-to-date on security patches. Does anyone have any suggestions? Thanks in advance for any advice.

Hello,A little surprise today while I was creating my playbook, it seems that the following actions are still using the CrowdStrike API endpoints that were decommissioned on September 30th. - detection_search : use /detects/queries/detects/v1- detection_aggregates : use /detects/aggregates/detects/GET/v1- update_detection : use /detects/entities/detects/v2- get_detection_details : use /detects/entities/summaries/GET/v1 In accordance with the CrowdStrike documentation, it appears that these API endpoints have been merged into the Alerts section. The documentation say "Detections are no longer stored in their legacy format."https://falcon.eu-1.crowdstrike.com/documentation/page/d02475a5/converting-from-detects-api-to-alerts-api# Could we please, in the next update, either remove these actions or update them to use the correct endpoints (for example, the ones already used in the update_alert action) ?

Hello FML admins, I am currently testing the Mail Migration feature in FortiMail to migrate email data from Gmail to FortiMail.I have followed the procedures outlined in the following documentation: https://docs.fortinet.com/document/fortimail/7.6.3/administration-guide/326016/migrating-email-from-other-mail-servers-server-mode-only#domain_user_1224406687_2752746https://community.fortinet.com/t5/FortiMail/Troubleshooting-Tip-FortiMail-migration-users-does-not-work/ta-p/306683 However, I consistently encounter an “Authentication failed” error during the migration process.Could you please confirm if there are any additional configurations or permissions that need to be set on the Gmail side to allow FortiMail to perform the migration successfully? Any tips would be much appreciated.Kind regards,

Hello,I'm new here, i have installed forticlient 7.4 in ubuntu 24.04.I was connected to my VPN server. after a week when i tried to reconect i had this error "config DNS failed".these are the logs from the forticlient:20241212 13:01:50.744 TZ=+0200 [sslvpn:INFO] main:2168 Init20241212 13:01:50.744 TZ=+0200 [sslvpn:INFO] main:2186 VPN is running in restore DNS mode20241212 13:01:50.750 TZ=+0200 [sslvpn:INFO] nettools:1854 More than one device with index 2 can be found20241212 13:01:50.751 TZ=+0200 [sslvpn:INFO] nettools:1854 Device address details: local_address xx.xx.xx.xx, device_index 2, device name eth0 (read from netlink)20241212 13:01:50.751 TZ=+0200 [sslvpn:INFO] nettools:1854 Device address details: local_address xxxx::xxx:xxxx:xxxx:xxxx, device_index 2, device name eth0 (read from netlink)20241212 13:01:50.781 TZ=+0200 [sslvpn:DEBG] vpn_util:299 Get connection name: netplan-eth020241212 13:01:50.791 TZ=+0200 [sslvpn:INFO] nmtools:865 Network Manager settings backup file doesn't

Hi there, is there a roadmap for supporting FortiEDR under macOS tahoe?We are currently using a 6.0.1.1022 version on macOS 15 but want to go forward to 26. Are there any plans on supporting it any time?Best regards

Simple question.  Should I be concerned that one FortiGate 101F consistently runs at 60% - 75% memory used, while a like 101F with a significantly larger network and hardware load uses 25% - 35% of memory on a daily average.Both 101s share the same OS version, internal hardware configuration, and basic firewall and SD-WAN configurations.  They differ in that the high-memory use 101 has three 4- port FortiSwitches serviced by FortiLink, roughly 14,000 entries in the routing table, and roughly 500 sessions.  The 101 using less memory hosts 10 48-port FortiSwitches, a 21,000 entry routing table, and roughly 4500 sessions.Neither 101 exhibits anomalous behavior at the moment.  Still, I wonder if I should expect trouble in the future.Thanks.

Hi everyone,I’m planning to upgrade a FortiGate 101F currently running FortiOS 7.0.8 to a newer 7.x version (likely 7.2 or 7.4).My client is a bit concerned about the BGP stability after the upgrade, since the FortiGate is currently handling BGP routing.Before proceeding, I’d like to ask if anyone has already performed this specific upgrade and could share their experience;Any issues encountered with BGP sessions, neighbors, or route redistribution after the upgrade.Whether you recommend going straight to 7.4.x or stopping at 7.2.x for now.Any insights, tips, or best practices would be greatly appreciatedThanks in advance for sharing your experience!

Hello, I have a specific deployement scenerio in my hand. My customer has a closed circuit production plant. There are handfull of PCs and a lot of cameras, industrial devices, industrial printers...etc. I have no problems with enviromental devices. The problem is this plant has limited internet connection and does not use LDAP. PCs are joined to a domain and configured in HQ. Then send to this plant. My question is: Can I use agent without LDAP integration for doing basic scans for applications and viruswall? Since there are no LDAP, I am thinking of using self signed certificates and trust them manually from client agents. But I still need to login to the agents, which I won't be able to match to an LDAP. I did some researchs, I have some ideas but I was not able to come up with a viable solution. If you guys can steer me to a right direction I will be glad.  thanks in advance.#fortinac

Hi everyone,I want to set up ipsec with FortiClient as dialup client (as mentioned here: https://docs.fortinet.com/document/fortigate/7.4.8/administration-guide/785501/forticlient-as-dialup-client).  Since ipsec seems to have way more options than ssl vpn - if I go trough the IPsec Wizard for remote access. Are these default settings ok (safe) to use?

I have Setup FSSO Collector Agent to be radius accounting server so that it monitors FSSO users and Radius Wifi users , NPS Server forward accounting requests to the FSSO but i have two problems with this setup:1- The FSSO Agent receives accounting stop messages ( confirmed through debug log) but it doesnt remove the user from login users list and neither tells fortigate to remove users 

From the debug, we can see that there is no problem with the time on both sides. 

Hi, On PSIRT i have now seen a few posts now where the solution for a CVE is to update to FortiOs 7.2.12.For example: https://fortiguard.fortinet.com/psirt/FG-IR-25-026But version 7.2.12 does not exist. Or am i confused?  BR,Arnold 

hello everybody: I installed a virtual machine on my computer (Oracle Virtual Box) to run behavior tests on my network. I noticed that even though it's not loaded, it browses normally. I'd like to know how to prevent any machine running in a virtual machine from browsing. I've tried to detect the virtual machine by MAC or IP, but I can't. How can I block virtual machines? I searched the security profiles and only found VMware. Can you give me some ideas on what to do?Thank you very much.

Hi everyone, Looking for help with a strange API authentication issue on one specific FortiGate. Setup:25 FortiGate firewalls managed via automated backup scriptUsing API v2 endpoint: /api/v2/monitor/system/config/backup?scope=globalSame API user (BACKUP-SUPER_ADMIN) configured on all devicesProblem: One firewall (let's call it FW-TEST) consistently returns HTTP 401 Unauthorized, while the exact same script works perfectly on the other 24 devices. What I've tried:Regenerated API token multiple timesVerified user permissions (identical to working firewalls)Manual test with Postman: same 401 errorGUI login with same account: works fineCompared API settings between working and non-working FW: no differences foundQuestion: Has anyone encountered a situation where one FortiGate rejects API authentication while others with identical config work fine? Could there be hidden settings or firmware-specific quirks that affect API token validation? Using FortiOS version if you k

I have been looking through the Fortimanager API documentation and there is a section mentioning running CLI commands against managed devices: https://how-to-fortimanager-api.readthedocs.io/en/latest/007_device_management/007_device_management.html#how-to-run-cli-commands-against-a-managed-device However, there is a warning message saying it is not yet supported and 'Caught in #1155085, #1072897 and #1133627.' I have tried it myself and get the same result as the example, so it definitely isn't working at the moment. I'm wondering if there is anywhere we can see where the progress of this is at- I have tried searching those aforementioned numbers which I assume are case tickets, but haven't found anything. It would be useful to have a timeframe on when this functionality might be made available.

Error message:/saml:Attribute></saml:AttributeStatement></saml:Assertion></samlp:Response>__samld_sp_login_resp [826]: Failed to process response message. ret=-111(Failed to verify signature.)samld_send_common_reply [91]: Code: 1, id: 539, pid: 5739, len: 64, data_len 48samld_send_common_reply [99]: Attr: 22, 12,samld_send_common_reply [99]: Attr: 23, 36, Failed to verify signature.samld_send_common_reply [119]: Sent resp: 64, pid=5739, job_id=539.[5739:root:0]epoll saml recv resp error.[5740:root:216]Timeout for connection 0x7f7ebad000. My SAML IDP uses Casdoor, which is an open source identity authentication system. I made sure my certificate is the public key certificate imported from the Casdoor system.

Hi, I've configured a ZTNA Server + Rule + Destination for RDP Session to a certain server.Therefore I configured a PROXY Port  which is then TCP Forwarding to Port 3389. Anyhow no RDP connection can be established.Any ideas? KR Chris

Hi,I am trying to connect a pair of Fortigate HA in A-P mode to 2 Aruba Core switches and wondering what the best practice is.  The Aruba switches are working in VSX mode.  Let's call them CS1 and CS2.  The connection will be like the following:CS1 port11 -> FG1 port 11CS1 port21 -> FG2 port 11CS2 port11 -> FG1 port 12CS2 Port21 -> FG2 port 12With VSX when connecting switches I can just put all 4 links in 1 LACP lag and it works fine. Now with interconnection between the Aruba switches and the Fortigate HA I am trying to find out what is the best option?  1. To put all 4 links in 1 multi-chassis lag on the Aruba side  and set lacp-ha-disable enable on the Fortigate side2. create 2 lags on the Aruba side, 1 lag to FG1 and another lag to FG2.What is the best practice here in terms of stability and failover time? Thanks,  

I see that starting from 7.4 we have an option to upgrade multiple ADOMs at once but they have to be on same version. https://docs.fortinet.com/document/fortimanager/7.4.0/new-features/107391/fortimanager-can-upgrade-multiple-adoms-same-version-at-the-same-time-7-4-1Is there any way to upgrade all ADOMs together regardless of current ADOM version ?

Hello,I’m trying to integrate SentinelOne with FortiSIEM following the official guide:https://docs.fortinet.com/document/fortisiem/7.4.2/external-systems-configuration-guide/780558/sentinelone According to the documentation, a “pre-defined HTTPS Credential Definition for the SentinelOne Singularity Activities API template” should be available for download. The Download Link: https://filestore.fortinet.com/docs.fortinet.com/fsiem/Public_Resource_Access/ESCG/SentinelOne/SentinelOne_Activities_https_advanced_definition.jsonHowever, when I click the provided link, it returns a 404 Not Found error, see the screenshot below:   If possible, could you please provide the JSON file or an updated link to download the SentinelOne HTTPS Credential Definition template?Thank you.

I am using IPSec to establish a VPN tunnel to the Fortigate. This works and I am able to ping multiple VLANs on our network. What I would like to do is have the VPN clients landing into VLAN_VPN, from that VLAN I want to use Firewall policy to allow the VPN Clients to other VLANS.I am able to do this, but the traffic always flow from VPN Interface to the other VLANs directly without forcing them through the VLAN_VPN. The Fortigate sees the other VLANs as directly connected, so the fortigate just sends the traffic directly from the VPN interface to the other VLANs. Any suggestions on how to accomplish forcing the traffic to the isolated VLAN_VPN and then using policy to allow traffic to the other VLANsThanksKevi n ThanksKevin

Description:Hello everyone,I’m facing a strange issue with our FortiGate 30E (firmware version 6.2.16). One of our internal staff networks uses a DHCP relay configuration. The relay forwards DHCP requests to a central DHCP server, from which devices such as computers and phones receive their IP addresses.Today we encountered a problem where some iOS devices (iPhone and iPad) couldn’t connect to the network via DHCP.Here’s what we observed:Not working:iOS 18.7.1iOS 18.6.2Working fine:iOS 18.3.2iOS 18.5iOS 26.01It seems that only newer iOS versions are failing to obtain an IP address through DHCP relay.Below is the configuration of the DHCP relay on the FortiGate interface:set dhcp-relay-ip "10.148.102.102"set dhcp-relay-type regularset dhcp-relay-agent-option enableset mtu-override disableset wccp disableset drop-overlapped-fragment disableset drop-fragment disableset interface "lan"set vlanid 79Has anyone experienced a similar issue where newer iOS versions fail to obtain an IP address

Dear Experts, At SD-WAN configuration, when manual mode is used, is "set priority-members" of "config service" stronger than "set priority" of "config members"?I tried several values and it seems to be such thing.Also, how should we use the both, including use of other modes? Thanks in advance, 

Hello Experts, I have an issue about site-to-site SD-WAN. Here is the situation.There are 2 ipsec tunnels between 2 Fortigates.One tunnel (called as X) is a simple ipsec tunnel.The other (called as Y) is a ipsec aggregation tunnel which has 3 ipsec tunnels (Y1, Y2, Y3)FG1 -- X ------- Network_A ------- X -- FG2    -- Y - Y1 -- Network_B -- Y1 - Y --         - Y2 -- Network_C -- Y2 -         = Y3 -- Network_D -- Y3 -(I hope you understand the above configuration.) When all Network_A,B,C,D belong to normal network, everything is ok.(Both X and Y are seen as green in SD-WAN performance SLA). However, when Network_B,C,D belongs to slow network such as satellite,Only X is OK (alive). Y is not alive as SD-WAN, although all ipsec tunnels (Y1, Y2, Y3)and aggregated Y are established as vpn tunnel.(Y is seen as red  in SD-WAN performance SLA, however all are seen as green in VPN page.) In this case of slow netw