Ad Widget

Collapse

WEB Monitoring - Error: Status code didn't match

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    WEB Monitoring - Error: Status code didn't match

    Hello everbody!

    I've got a question about ZABBIX WEB Monitoring.
    I configurated a Scenario, but the Login didn't work.

    My configuration:
    Scenario:
    Application: Hosting Service
    Name: Sharepoint
    Update interval (in sec): 30
    Agent: IE
    Status: Active
    Variables: {user}=<admin @ domain.ch>
    {password}=<password>


    Steps:
    Name: Login
    URL: https://<sharepoint>
    Post: name={user}$password={password}$enter={Enter}
    Timeout: 15
    Required:
    Status codes: 200


    The problem is, in the WEB Monitoring stands Failed on "Login" [1 of 1] Error: Status code didn't match.
    Return Code is 401, but i the Return Code wan't 200.

    Can someone help me?
    Sorry about my English(Switzerland )...

    #2
    1/ Are you sure sharepoint accepts authentication from POST variables ?
    2/ Use curl to test you scenario (man curl !). As far as I know, zabbix_server cannot (yet ?) respond to authentication challenges.

    Comment


      #3
      i have same problem. who solved a problem?

      Comment


        #4
        When your Uptrends monitor detects an error, the check detail and monitor logs display an error code based on the event or problem. The following list contains the codes and detailed descriptions for the error codes, and in some cases, the description includes possible causes and corrective actions you may take.

        Comment


          #5
          Originally posted by Calimero View Post
          1/ Are you sure sharepoint accepts authentication from POST variables ?
          2/ Use curl to test you scenario (man curl !). As far as I know,
          9apps download
          zabbix_server cannot (yet ?) respond to authentication challenges.
          I think I am also facing this issue. Did you get any proper solution?
          Last edited by William138; 13-03-2019, 12:42.

          Comment

          Announcement

          Collapse
          No announcement yet.
          Working...
          X