For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8

The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results.

I made a simple fix and submitted it as PR to the bitbucket repository.

I‘m happy to merge the PR after a quick test next week.

Stefan

Dear all, 

we have a running elog installation using SSL (with the self-signed certificate). Generally we use the web interface, but we have been asked if it was possible to automatically insert elog entries via command line. 

elog.exe should be the answer and so I gave it a try.

I was trying the following command line: 

elog.exe. -h server-ip-address -p 8080 -l demo -s -v -u username password -a "Mass=0" This is a test entry

Of course server-ip-address and username / password were proper fields. 

When I was doing this from the server itself, I got the following message:

Successfully connected to host server-ip-address, port 8080
Possibly invalid certificate, continue on your own risk!

and then the entry was inserted, but when I was typing the same from any other PC I got the error message:

Successfully connected to host server-ip-address, port 8080
elogd server does not run SSL protocol

The entry is of course not added and also the server (that is running in very verbose mode) reported a

SSL_accept failed

How can I fix it?  

Thanks for helping,

Antonio

Hello,
I have experienced some inconveniences with the restrict edit time option.

First, it is not possible for admin users to edit an entry after the edit time.
The restrict edit option allows admin users to edit posts from other users,
so I think admins should also be allowed to edit posts after edit time.
As they can edit the config and temporarily disable the restrict edit time option, which is an issue.

Secondly, if a user made a draft and did not submitted it before the edit time runs out,
the draft got stuck as it cannot be edited (and submitted) any more.

Best wishes,
Sebastian

Any news for my problem? 

Your help is very much appreaciated! 

thanks :)

I am using SSL with ELOG and it works fine with the "elog" executable. I am no expert on SSL, but I can provide my two cent what you could try, maybe it helps:

• SSL desires to run on the port 443 - I have no idea if you can force it to run on an arbitrary port, it might be possible. But does it make sense?
• Certificates are checked against the provider of the certificate. I guess this works fine from your web browser? Or did you just add a security exception?
• Has the installed "elog.exe" been compiled with SSL support on?

Dear Andreas,

thanks for your message.

Here are the answers to your questions.

• Tomorrow I will try to restart the server on port 443, at least temporary, to see if it makes any difference
• We don't have a real certificate, but just the self-signed certificate that comes with the standard distribution of elog. Of course, I have to accept an exception when connecting from the browser. When I try to add an entry to via the command line from the server itself, I get the message Possibly invalid certificate, continue on your own risk! but it works. 
• I hope so. This is the elog.exe that comes with the standard distribution, so I have to presume so. It is the same version that is installed on the server, where it works.

Thanks again and more tomorrow...

As promised, here is the results of the additional debugging. 

Changing to port 443 doesn't help. I keep having exactly the same behaviour, it is to say: 

• from the server itself I get