Thanks for answering. Just tried your suggestion with different browsers
(firefox, chrome, brave) but the error message still appears when adding a
new user.

By the way, i justed noticed that if you click "back" followed by "cancel" you
enter the logbook as the user you just added. It seems that although elogd
throws an error, the user is added. Weird.

Since most of our users don't trust open source software, the error message
will only confuse them. So, is there any way to avoid this message from
appearing?

Perhaps a few words about our use case:
We are a german non profit organisation in disaster control. Since 2007 we use
elog as mobile mission journal in our unit. We adapted elog to run from
usb-stick, so all our first-responders have to do is to plug it into a laptop
and they are ready to go.
We also hand the adapted installation to other organisations like local fire
department or red cross units and offer them a short (2 hour) course on how to
use it. Since the windows-release is the most requested, it would be confusing
for them if an error message appears every time a new user is added.

So if you have any further ideas, I would appreciate that.

Uwe

>       Error: Command "config" is not allowed for user ""

Could it be related to the error messages thrown by "activate user"? see
https://elog.psi.ch/elogs/Forum/69479

K.O.

Hello,

Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.

1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.

Hello,

what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:

Subst Author = $long_name from $remote_host

Subst Email = $user_email

in the elogd.cfg file does not seem to work.

(I see it works here on this platform)

Tnks

G

You need user-level access control, using 

Password file = ...

Stefan

Thank you but that is already  in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.

tnks

g

If you would post a minimal config file where the problem occurs, then we could look what the problem is.

[global]

port = 8080

ssl = 0

Password file = passwords.txt

Admin user = user1

SMTP host = smtp. mail.com

SMTP port = 25

SMTP username = user1@mail.com

SMTP Password = GIwbx7UbmkWs5J0P8lVztX7Anje0/21BU/Tmk0aPm.

Logfile = ELog_log.txt

Logging level = 3

[Server]

Logbook dir = Server

Theme = default

Comment = Server Change Log

Attributes = Author, Email, Type, Category, Subject

Subst Author = $long_name from $remote_host

Subst Email = $user_email

Options Type = SRV 1, SRV 2, SRV Sup, BMS content, BMS setpoints, BMS new

Options Category = Config, User, Access, Connection, Change, New, Delete

Extendable Options =

Required Attributes = Author, Type

Page Title = ELOG - $subject

Reverse sort = 1

Quick filter = Date, Type