linux web interface

Discussion in 'ESET Smart Security v3 Beta Forum' started by Jdeane, Oct 3, 2007.

Thread Status:
Not open for further replies.
  1. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    i'm having problems trying to get the linux web interface to work.


    I've installed the latest beta and have edited the esets.cfg file as shown below, I restart the app but when I try to browse using the local pc http://127.0.0.1:8081 it returns 'could not connect to host 127.0.0.1 (port 8081)'

    If i browse to http://127.0.0.1 i get the normal Apache welcome screen.

    What else needs setup?


    Jon

    [wwwi]
    # Settings for ESETS Web Interface configuration module

    # agent_enabled = yes/no
    # Enables operation of the esets_wwwi.
    agent_enabled = yes

    # listen_addr = "address"
    # Address (IP or name) where esets_wwwi listens for HTTPS client connections.
    # If set to 0.0.0.0 then esets_wwwi listens on all available network interfaces.
    listen_addr = "0.0.0.0"

    # listen_port = port
    # TCP port where esets_wwwi listens for HTTPS client connections.
    # You may have to open this port in your firewall.
    listen_port = "8081"

    # username and password needed for accessing the interface (required)
    username = "admin"
    password = "admin"
     
  2. Tomas_h

    Tomas_h Registered Member

    Joined:
    Oct 4, 2007
    Posts:
    1
    wwwi agent uses secure conection https.

    Try to use IP that has been assigned to your LAN by your provider. For example my IP is 192.168.1.1 so I use https://192.168.1.1:8081.
     
  3. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    still getting the failed to connect https:\\192.168.42.160:8081

    3 of us have been trying to test this on different pc's and none of us can get this to work.

    Jon
     
  4. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    if you're on your linux machine, use:

    http://127.0.0.1:8081

    of - whatever your linux machine's IP is - the example 192.168.1.1 would only work if you are using that private network IP - 127.0.0.1 being localhost, should work if you're using the workstation itself.
     
  5. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    as stated tried https and http nither connect to the local address at port 8081

    using http://127.0.0.1 brings up the normal Apache welcome screen adding :8081 results in an unable to open message.
     
  6. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    are you sure that the service has been started on the linux box?
     
  7. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    i've been using the command '/etc/init.d/esets_daemon restart' each time I make a change to the config.

    [root@jon-linux ~]# ps -fade | grep ese
    root 2523 1 0 09:49 ? 00:00:00 /usr/sbin/esets_daemon
    root 2524 2523 0 09:49 ? 00:00:01 /usr/sbin/esets_daemon
    root 4393 4379 0 12:58 pts/1 00:00:00 grep ese
    [root@jon-linux ~]# ps -fade | grep nod
    root 1912 1 0 09:00 ? 00:00:00 /bin/sh /etc/X11/prefdm -nodaemon
    root 1941 1912 0 09:00 ? 00:00:00 /usr/sbin/gdm-binary -nodaemon
    root 1966 1941 0 09:00 ? 00:00:00 /usr/sbin/gdm-binary -nodaemon
    root 4395 4379 0 12:58 pts/1 00:00:00 grep nod

    not sure if the last ps for nod reflects Eset or other linux modules.

    Do you have to start the web part seperatly? if so how?

    Jon
     
  8. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    anyone any more thoughts?

    Jon
     
  9. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    other than you have the linux firewall blocking 8081, no - I have no more ideas. Are you running ipchains or iptables or some other kind of firewall on the machine?
     
  10. Jdeane

    Jdeane Eset Staff

    Joined:
    Jul 18, 2007
    Posts:
    82
    Location:
    UK
    no firewall running at all. 3 of us have tried, each with a different flavour of Linux and none of us have got it to work. Starting to think it is a myth regarding the web interface...
     
  11. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    I'll try tomorrow if I get time, I have 4/5 nix machines in the office.
     
Thread Status:
Not open for further replies.