Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   How to not expose elog port when running under a reverse proxy, posted by Nicola on Mon Jan 22 08:22:33 2024 
    icon2.gif   Re: How to not expose elog port when running under a reverse proxy, posted by Frank Heyroth on Mon Jan 22 20:50:50 2024 
Message ID: 69724     Entry time: Mon Jan 22 20:50:50 2024     In reply to: 69722
Icon: Reply  Author: Frank Heyroth  Author Email: heyroth (at) cmat.uni-halle.de 
Category: Question  OS: Linux  ELOG Version: V3.1.3-7933898 
Subject: Re: How to not expose elog port when running under a reverse proxy 

Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1
port = 8080

however than this can be changed by any user how has global admin rights in elog.

So I changed the line in the elogd.service startscript
ExecStart=/usr/local/sbin/elogd -D -p 8080 -n 127.0.0.1  -c /usr/local/elog/elogd.cfg

I hope this has the priority (not tested).

 

Nicola wrote:

I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed, but I cannot find how to configure the elog server to expose it only locally

 

ELOG V3.1.5-fe60aaf