Skip to main content
Kevinblac
Kevinblac
New Member
October 16, 2023
Solved

Cannot use CLI

  • October 16, 2023
  • 4 replies
  • 4306 views

Folks,

For some reason am unable to run any commands on the CLI yet i am using the default admin user. All commands are failing with the "parsing" error. 

See attached screenshot.

What would i be doing wrong?

config error.png

Best answer by Kevinblac

Dear all,

Was able to solve the problem. The issue was with the file path, so i had to key in "config global" to go to global config or config vdom to config anything on the vdom. 
Issue is now sorted. Thank you all for your suggestions/replies.

4 replies

kumarh
Staff
kumarh
Staff
October 16, 2023

Which firmware version you are running?

    Kevinblac
    KevinblacAuthor
    New Member
    October 16, 2023

    FortiWeb-400E
    v7.2.1 build330 (GA)

    Kevinblac
    KevinblacAuthor
    New Member
    October 17, 2023

    Have upgraded to version 7.4 but still can do any commands on cli..
    error fortiweb.png

    srajeswaran
    Staff
    srajeswaran
    Staff
    October 17, 2023

    I have seen this issue when there is no space left on the device. Can you connect to console and check if there are any alerts/errors ?

      Sheikh
      Staff
      Sheikh
      Staff
      October 17, 2023

      This might also cause if the command syntax is incorrect. Please see the FortiWeb CLI reference below.

       

      When entering a command, the CLI requires that you use valid syntax and conform to expected input constraints. It will reject invalid commands.

      For example, if you do not type the entire object that will receive the action of a command operator such as config, the CLI will return an error message such as:

      Command fail. CLI parsing error

       

      https://docs.fortinet.com/document/fortiweb/7.4.0/cli-reference/909750/command-syntax

       

      regards,

       

      Sheikh

      Kevinblac
      KevinblacAuthorAnswer
      New Member
      October 19, 2023

      Dear all,

      Was able to solve the problem. The issue was with the file path, so i had to key in "config global" to go to global config or config vdom to config anything on the vdom. 
      Issue is now sorted. Thank you all for your suggestions/replies.

      srajeswaran
      Staff
      srajeswaran
      Staff
      October 19, 2023

      FortiWeb or Fortigate?

        Kevinblac
        KevinblacAuthor
        New Member
        October 19, 2023

        Fortiweb

        Terms & ConditionsAccessibility statement