Results 1 to 2 of 2

Thread: can't connect to web inteface, webui

  1. #1
    Junior Member
    Join Date
    Apr 2015
    Posts
    5

    can't connect to web inteface, webui

    I can't connect to webui
    I have an error message in brokerd.log
    [1439791474] WARNING: [broker-master] Failed to authenticate user, return false

    i use modules auth-htpasswd
    I generate htpasswd.users file
    Also i have the module auth-htpasswd with /etc/shinken/htpasswd.users


    webui.cfg
    ## Module: webui
    ## Loaded by: Broker
    # The Shinken web interface and integrated web server.
    define module {
    module_name webui
    module_type webui
    host 0.0.0.0 ; All interfaces = 0.0.0.0
    port 7767
    auth_secret admin ; CHANGE THIS or someone could forge cookies
    allow_html_output 1 ; Allow or not HTML chars in plugins output.
    ; WARNING: Allowing can be a security issue.
    max_output_length 1024 ; Maximum output length for plugin output in webui
    manage_acl 1 ; Use contacts ACL. 0 allow actions for all.
    play_sound 0 ; Play sound on new non-acknowledged problems.
    login_text Welcome on Shinken WebUI RL ; Text in the login form.

    ## Modules for WebUI
    # - auth-htpasswd = Use an htpasswd file for auth backend.
    # - auth-active-directory = Use AD for auth backend (and retrieve photos).
    # - auth-cfg-password = Use the password setted in Shinken contact for auth.
    # - ui-pnp = Use PNP graphs in the UI.
    # - ui-graphite = Use graphs from Graphite time series database.
    # - mongodb = Save user preferences to a Mongodb database
    # - SQLitedb = Save user preferences to a SQLite database
    modules
    ## Advanced Options
    # Don't play with them on your production server
    #http_backend auto ; Choice is: auto, wsgiref or cherrypy if available
    #remote_user_enable 1 ; If WebUI is behind a web server which
    ; has already authentified user, enable.
    #remote_user_enable 2 ; Look for remote user in the WSGI environment
    ; instead of the HTTP header. This allows
    ; for fastcgi (flup) and scgi (flupscgi)
    ; integration, eg. with the apache modules.
    #remote_user_variable X_Remote_User ; Set to the HTTP header containing
    ; the authentificated user s name, which
    ; must be a Shinken contact.
    # If you got external plugins (pages) to load on webui
    #additional_plugins_dir
    modules auth-htpasswd
    }

  2. #2
    Junior Member
    Join Date
    May 2014
    Location
    Bordeaux - France
    Posts
    17
    Hi,

    I see to module variable in your configuration.
    I think you need to configure the webui.cfg like this :

    webui.cfg
    ## Module: webui
    ## Loaded by: Broker
    # The Shinken web interface and integrated web server.
    define module {
    module_name webui
    module_type webui
    host 0.0.0.0 ; All interfaces = 0.0.0.0
    port 7767
    auth_secret admin ; CHANGE THIS or someone could forge cookies
    allow_html_output 1 ; Allow or not HTML chars in plugins output.
    ; WARNING: Allowing can be a security issue.
    max_output_length 1024 ; Maximum output length for plugin output in webui
    manage_acl 1 ; Use contacts ACL. 0 allow actions for all.
    play_sound 0 ; Play sound on new non-acknowledged problems.
    login_text Welcome on Shinken WebUI RL ; Text in the login form.

    ## Modules for WebUI
    # - auth-htpasswd = Use an htpasswd file for auth backend.
    # - auth-active-directory = Use AD for auth backend (and retrieve photos).
    # - auth-cfg-password = Use the password setted in Shinken contact for auth.
    # - ui-pnp = Use PNP graphs in the UI.
    # - ui-graphite = Use graphs from Graphite time series database.
    # - mongodb = Save user preferences to a Mongodb database
    # - SQLitedb = Save user preferences to a SQLite database
    modules auth-htpasswd
    ## Advanced Options
    # Don't play with them on your production server
    #http_backend auto ; Choice is: auto, wsgiref or cherrypy if available
    #remote_user_enable 1 ; If WebUI is behind a web server which
    ; has already authentified user, enable.
    #remote_user_enable 2 ; Look for remote user in the WSGI environment
    ; instead of the HTTP header. This allows
    ; for fastcgi (flup) and scgi (flupscgi)
    ; integration, eg. with the apache modules.
    #remote_user_variable X_Remote_User ; Set to the HTTP header containing
    ; the authentificated user s name, which
    ; must be a Shinken contact.
    # If you got external plugins (pages) to load on webui
    #additional_plugins_dir

    }

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •