Menu

anyone have "remote" working

Help
Nic
2004-02-11
2013-04-15
  • Nic

    Nic - 2004-02-11

    Anyone have this working?  The documentation points to a template directory that is not created with the RPM install.

     
    • Nic

      Nic - 2004-02-11

      diregard this, see jdklusman's writeup

       
    • BrianRoper

      BrianRoper - 2005-01-24

      Yes thanks, remote web interface works fine.

       
      • caminoix

        caminoix - 2005-03-28

        ee, sorry, but i'm a newbie to linux. could you please explain it in a more idiotproof way?

        i read the doc on the mutella homepage - what is 'RemotePass' &c.? (see http://mutella.sourceforge.net/readme.php\)

        help me, please

         
    • BrianRoper

      BrianRoper - 2005-04-03

      Have you read the readme and man page about this ?
      "NEW: Since version 0.3.9b mutella provides built-in HTTP interface, which,
      however, is disabled by default in order to guaranty high security of the
      default configuration. The procedure of activation of the remote interface
      is briefly described in the HTTP-interface section."
      and
      "HTTP-interface
      ==============

      Since version 0.3.9b mutella provides built-in template-based HTTP
      interface. The default location of the template files is
      '/usr/local/share/mutella/remote/template/'.
      The access to the remote interface is disabled by default in order to
      ensure that high security and privacy traditionally provided by mutella
      is maintained. To enable http-ui one has to:
      1. Set remote username/password via 'RemotePass' and 'RemotePass' variables
      2. Set 'RemoteEnable' to 'true'
      3. Set 'AllowedRemoteNet' to something appropriate if http-ui is supposed
         to be used from somewhere else. The default is 'localhost only' that is
         '127.0.0.1/32'. To enable any IP to use the HTTP interface set
         'AllowedRemoteNet' to '0.0.0.0/0'.

      To connect to the http interface type 'http://localhost:6346/remote' in
      your favourite browser (this implies that your client is listening on port
      6346; check 'LocalPort' if this does not work).

      TIP: if you set 'AllowedRemoteNet' to your private class-C subnet like
      '192.168.1.0/24' it is important to realise that the 'localhost' is no
      longer allowed to use the UI. The workaround is to use the host name instead
      of the 'localhost' in the browther.

      For troubleshooting is it helpfull to check HTTP access log file located at
      '~/.mutella/htaccess.log' The logging facility may be switched off by setting
      'RemoteLogAccess' to 'false'

      NOTE: The template pages for the remote interface are installed to
      /share/mutella/remote/template by default. The place where mutella
      looks for the template is controlled by 'RemoteTemplatePath' variable.
      This variable will point to the correct location if you have installed
      mutella using 'make install' or as a binary package. Othervise you have to
      adjust 'RemoteTemplatePath' to point ot the correct directory on your file
      system. Mutella's built-in HTTP server does not allow '..' path elements and
      does not build directory indexes for security reasons."

      Do you have port 6346 open ?

      - BG

       

Log in to post a comment.