Unable to execute conduit commands restore_factory or restore_defaults via API.

Home Forums Conduit: AEP Model Unable to execute conduit commands restore_factory or restore_defaults via API.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #30574
    Ajay K
    Participant

    Calling either the restore_factory or restore_defaults in conduit firmware version 5.1.6 via the conduit API results in unknown command error as mentioned below.

    Here is the raw get request logged in fiddler

    GET https://192.168.2.2/api/command/restore_defaults HTTP/1.1
    Host: 192.168.2.2
    Cookie: token=B85C68E897ACBD9320C0B77A56271444

    And the raw response logged in fiddler.

    HTTP/1.1 400 Bad Request
    Set-Cookie: token=B85C68E897ACBD9320C0B77A56271444; Path=/; Secure
    Cache-Control: no-cache
    Content-type: application/json
    Access-Control-Allow-Origin: *
    Content-Security-Policy: default-src 'self'; script-src 'unsafe-inline' 'unsafe-eval' 'self'; style-src 'unsafe-inline' https://fonts.googleapis.com 'self'; font-src https://fonts.gstatic.com 'self'; connect-src 'self'; img-src 'self' data:
    X-Frame-Options: SAMEORIGIN
    X-XSS-Protection: 1; mode=block
    X-Content-Type-Options: nosniff
    Referrer-Policy: strict-origin-when-cross-origin
    Feature-Policy: accelerometer 'none'; camera 'none'; geolocation 'none'; gyroscope 'none'; payment 'none'; usb 'none'
    Strict-Transport-Security: max-age=31536000
    Content-Length: 74
    Date: Wed, 06 May 2020 19:07:43 GMT
    
    {
       "code" : 400,
       "error" : "unknown command",
       "status" : "fail"
    }

    This used to work and all of a sudden it’s throwing this error, when called via the API.

    Thanks,
    Ajay

    #30575
    Jeff Hatch
    Keymaster

    Hello Ajay,

    Does it give the same error if you change it to a POST instead of a GET?

    Jeff

    #30576
    Ajay K
    Participant

    Thanks Jeff, that was it. I think I had at some point was testing with a POST request and it worked and somewhere down the line must have accidentally changed it to a GET request. Thanks as always for your help.

    Thanks,
    Ajay

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.