PDA

View Full Version : linux web interface


Jdeane
October 3rd, 2007, 11:35 AM
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"

Tomas_h
October 4th, 2007, 12:12 AM
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.

Jdeane
October 4th, 2007, 04:12 AM
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

webyourbusiness
October 4th, 2007, 09:14 AM
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.

Jdeane
October 5th, 2007, 05:41 AM
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.

webyourbusiness
October 5th, 2007, 10:15 AM
are you sure that the service has been started on the linux box?

Jdeane
October 10th, 2007, 05:33 AM
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

Jdeane
October 17th, 2007, 09:38 AM
anyone any more thoughts?

Jon

webyourbusiness
October 17th, 2007, 09:43 AM
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?

Jdeane
October 17th, 2007, 09:55 AM
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...

webyourbusiness
October 17th, 2007, 09:22 PM
I'll try tomorrow if I get time, I have 4/5 nix machines in the office.