When you run a script on the web GUI/interface:If it fails, it provides absolutely no diagnostic debugging output to the user about why/where? I implore Fortinet, I beg you, please provide diagnostic output about the line number and/or command line that fails. Otherwise, we’re just guessing by taking shots in the dark; not a professional troubleshooting technique. Pasting the same script into the CLI is not the same execution environment as uploading it via the GUI. So one cannot reliably assume that warnings and errors will manifest the same. BONUS: It creates a historical event object (pass or fail run record), so why not save/cache the script code itself, and allow the user to “re-run” it ?

G

GEHCS

Visitor III

Question

[Feature Request] FortiOS: Run Scripts via Web GUI - Diagnostic Debug Output

Forum|Forum|19 days ago
June 29, 2026
1 reply
36 views

When you run a script on the web GUI/interface:

If it fails, it provides absolutely no diagnostic debugging output to the user about why/where?
- I implore Fortinet, I beg you, please provide diagnostic output about the line number and/or command line that fails.
  - Otherwise, we’re just guessing by taking shots in the dark; not a professional troubleshooting technique.
  - Pasting the same script into the CLI is not the same execution environment as uploading it via the GUI. So one cannot reliably assume that warnings and errors will manifest the same.
BONUS: It creates a historical event object (pass or fail run record), so why not save/cache the script code itself, and allow the user to “re-run” it ?

Markus_M

Staff & Editor

Hey,

I’m curious - what scripts (there are multiple variants)?
> Pasting the same script into the CLI is not the same execution environment as uploading it via the GUI. So one cannot reliably assume that warnings and errors will manifest the same.

I would normally assume so, I only know that running a function via UI and another via CLI can output different results, but the scripts I’ve been using hadn't been affected by that.

BSeklecki_GEVernova

Explorer II

In the CLI, if you run a purge command, you can add an extra “y” after a CR/LF character, to answer the newly mandated user interactions (confirmations).

Whereas doing so on the web GUI upload function is just a plain syntax error.

NOTE: The inability to define an environmental variable to override the user-interaction-confirmation on the PURGE function is itself another topic for another feature request on another morning. Its becoming eerily like PowerShell, where certain commands ignore -prompt:$false

#BOFH #BOFHMode

My question is: Is this a $10,000 GNU/Linux box or not? >:}

Sign up

Login with SSO

Login to the community

Login with SSO