I've been trying to configured a Synology NAS to run my personal elog with a reverse proxy to the outside world.  The best way seems to be running Elog in a Docker instance and then running a separate connected Docker running a nginx-proxy (in this case jwilder/nginx-proxy). This second container manages the certificates to letsencrypt and mapping URL requests to relevant containers so that connection is secured properly.  

It worked great in the initial test. However, I have an issue with authentication.  When I password protect the elog it goes to a login page.  When I give an correct password it loops back to the login page (incidentally when I give an incorrect password it gives an 'Invalid user name or password!' warning).  So I know that its getting the correct password but there is some issue that is resetting or ignoring the authentication.  I am never able to actually get to the protected content. 

Does anyone have any experience in using Nginx to setup a secure reverse proxy? Any insights into why this would mess with the authentication of elog?

Side note: I have tried using Apache to do the same and authentication worked fine.  But the pre-canned jwilder/nginx-proxy docker manages all the certificates automatically and seamlessly and allows me to have multiple services running on the same outward facing port on my router.  There is no equivalent (as far as I know) that uses Apache for proxying with letsencrypt​.

When using the Webserver authentication in combination with "File" and "Self register = 3", it is possible to keep track of registrations and control access still. This is very useful, and upon clicking on the logbook for the first time, the user is asked to register by typing their username, full name and email address.

First issue here is that they can still edit the box with their username, which might cause confusion if somebody decides to choose a different username and is then surprised about why they cannot automatically login again. Is it possible to lock this field from being edited?

The second issue is more minor, but the user has to manually type their name and email address, even though the webserver may already be able to provide this information in the headers. Specifically, it would be useful to read the name from the X-Forwarded-Name header and email address from the X-Forwarded-Email header. 

My config file snippet is below:

Authentication = Webserver, File
allow password change = 0
Password file = webserver.passwords
Self register    = 3
 

We are using the Elog client from one vlan to insert entries into our Elog system on a different vlan.

Works fine for the most part but we occasionally have network connection issues which prevents some entries from being added, and we don't find out about it until later.

Is there a Return Code associated with the client pgm? Or some suggestion to promptly verify a successful enrty? (We'd queue and resubmit in bulk once running again, if we knew about it.)

Thanks.

Hello,
Elogd crashing when "Resubmit as new entry" is executed.
Tried with demo config, same result, also tried with snapshot version.
After the first crash i restart elogd, then it crashes every time i enter 
the logbook containing the entry i tried to "Resubmit as new entry"
Anyone seen same behavior, on win2000 platform ?.

Miljan

I am working on a logbook for a lab.  I have two questions...
First - Some of the logbook entries should not be viewed by certain users.  
What would be the easiest way to restrict viewing some entries?  

Second - I have a welcome page for the ELOG that lists some info about the 
ELOG.  When I start the ELOG, the user sees the login page.  After the user 
logs in, the welcome page appears listing the restrictions.  Right now, I 
have a hyperlink that takes the user to new, find, etc.  But I would like 
to take the user right to the logbook and not have to come back to the 
welcome page everytime.  How can I do this?

I have attached the code I have so far.  They are in .txt format for easier 
viewing.

Thanks!

Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry?  I know it is possible to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering if this is possible currently, or if this is planned, or could be planned for a future version?

Thanks,

Allen