> Like many educational institutions we get "educational certificates" that are chain certificates..
>  
> only shows: 
> 
> CONNECTED(00000003)
> 25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:
> 
> What do I do wrong?
> 

After reading the OpenSSL Documentation:

The certificates must be in PEM format and must be sorted starting with the subject's certificate (actual client or
server certificate), followed by intermediate CA certificates if applicable, and ending at the highest level (root) CA.

The chain.crt has to be of the following format:

HOST CERTIFICATE
INTERMEDIATE CERTIFICATE
ROOT CERTIFICATE

Then it is working w/o problems

GS

How did you create the certificate?
Are you running eLog on a server with more than one host name (CNAME entries) and are you pointing to your eLog
via one of that aliases?

Certificates that work with an Apache 1 Web server do work with eLog, too.

GS

> 
> The certificate that is on there right now is the one that gets created when you install elogs.  I have tried 
> creating one with a windows server 2008 box with the CA role installed.  The certificate is created without issue 
> and I can install it on the server but when I try to restart the elog service it wont start until I put the 
> original server.crt and server.key file back into the ssl directory.  
> 

I don't know anything about Windows server CA, but eLog is very strict in the syntax of the CERTs.
I had to learn it the hard way when installing a chain CERT.

For server.crt and server.key it MUST NOT be a chain cert. Therefor you have to use chain.crt

Are the generated CERTs ASCII (with only one -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- in
server.crt 
and -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- in server.key)?

So the eLog generated keys should look like..

GS

Let me start by saying that I really like ELOG-- it's a nice tool.

I'm trying out version 2.3.3. The problem that I'm having is with
attachments disappearing when I do the following:

1. create a new entry that contains one or more attachments.
2. verify that the new entry from step 1 saved correctly.
3. reply to the entry from step 1.
4. return to the entry from step 1 only to find the attachments gone.

The attachement files are still in the logbook directory, it's just that
they are no longer attached to the entry.

FWIW, I've attached the elog.config that I'm using...

Thanks,

Greg

I'm interested using elog for a lab notebook.  Once entries have been
entered they cannot be changed/edited.
Is it possible for elog to be setup to support something like this?  A write
only mode?

Does this truly disable the edit command or just hide it?

> > I'm interested using elog for a lab notebook.  Once entries have been
> > entered they cannot be changed/edited.
> > Is it possible for elog to be setup to support something like this?  A write
> > only mode?
> 
> What you need is an entry in the elogd.cfg file:
> 
> Manu commands = Back, New, Reply, Find, Config, Logout, Help
> 
> As you see, the "Edit" and "Delete" commands are missing here and therefore 
> do not get displayed. So you can enter a message with "New", but you cannot 
> change it afterwards.

The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
aggregators to fail when parsing.

The error is shown by Feedvalidator:
http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Fmidas.psi.ch%2Felogs%2FForum%2Felog.rdf

> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
> 
> For an introduction to RSS feeds, please see 
> 
> http://www.webreference.com/authoring/languages/xml/rss/intro/
> 
> To subscribe to a logbook, enter following URL into your RSS reader:
> 
> http://<your-elog-host.domain>/<logbook>/elog.rdf
> 
> From the newest Mozilla Firefox browser, you can also click on the RSS box at
> the lower right corner of the browser (see attachment).

I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the formatting issue, and I could make this go away with a kill...restart cycle of elogd.

I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.

I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.

Any thoughts about what the problem is?