Hey everyone,
I’m running into a weird issue and figured someone here might’ve dealt with something similar.
I’m trying to block Spotify using Application Control in an outgoing policy (FortiOS 6.2) — I’ve added it as an override with the action set to “Block.” Sounds simple enough, right? But when I check the traffic logs and filter for Spotify, it’s still showing as "pass" under action.
I’ve triple-checked that it’s the right policy being applied and that the profile with the override is definitely attached — so I don’t think it’s a misconfiguration on the policy side.
To be thorough, I also went through a few related posts:
Unfortunately, none of these seem to fix the issue for me. I’m starting to wonder if I’m missing something subtle in the Application Control Profile settings — like maybe an extra step or checkbox that’s needed for the override to actually kick in?
If anyone’s run into this kind of behavior before or has any troubleshooting tips, I’d really appreciate the help. This one’s got me scratching my head. Thanks in advance!
Hello,
I would like to double check whether the unit is running FortiOS 6.2 or 7.2 branch. FortioS 6.2 branch reached end of support a few years ago.
Spotify signature was relatively recently updated and doesn't require deep inspection:
https://www.fortiguard.com/appcontrol/17405
User | Count |
---|---|
2561 | |
1357 | |
796 | |
650 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.