Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 317 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 316, 317, 318 ... 805, 806, 807   Next  
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  68833   Tue Aug 14 06:04:53 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Other3.1.2Re: Reverse proxy of Elog using Docker and Nginx?

Have you tried the "URL = ..." statement? This determines you elog redirects if you log in. If you reach elog through a proxy, the URL is a different one that if you access it directly. In your case the proxy URL might be necessary.

Stefan

Andrew Wade wrote:

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​.

 

  68836   Mon Aug 20 12:42:24 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Other3.1.2Re: Reverse proxy of Elog using Docker and Nginx?

Actually this forum works through an Apache reverse proxy with authentication and it works, so I suspect that the problem has to do with jwilder/nginx-proxy. Since we don't have this here, all I can propose is that you do debugging yourself. Run elogd with the -v flag so that you see all requests coming from the user through the proxy. Compare the requests through Apache and Nginx to see if any argumets are stripped or mangled. Upon successful login, elog sets a cookie with a unique session-ID (the cookie name is "sid") to the browser. If you proxy strips that cookie, you would land on the login page. Maybe look in that direction.

Stefan

Andrew Wade wrote:

Yes, I tried setting the URL parameter to the url used by the proxy.  It goes to the correct address but that landing is the login page.

Andrew

Stefan Ritt wrote:

Have you tried the "URL = ..." statement? This determines you elog redirects if you log in. If you reach elog through a proxy, the URL is a different one that if you access it directly. In your case the proxy URL might be necessary.

Stefan

Andrew Wade wrote:

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​.

 

 

 

  68837   Mon Aug 27 13:07:28 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification

That's how it is implemented. If you use

Max email attachment size = 1000000

then attachments below 1 MB are sent as attachments, and if the attachment is above 1 MB, then only a link to the attachment in the elog is sent.

Stefan

Lars Martin wrote:

Wouldn't it make sense for ELog (by default) to still notify, but not send the attachments by e-mail if the size limit is reached?

Andreas Luedeke wrote:
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But I think that an 2.2 MB image should easily fit into that.
Andreas
Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

 

  68840   Wed Sep 12 11:10:18 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog source

This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(), which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please post the full warning list here.

Stefan

  68847   Fri Oct 12 10:17:20 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.1-0767eb0Re: Buttons missing in ckeditor

Have you selected "HTML" encoding (below the main message box). The HTML editor is not activated if you have "plain" text encoding. Did you try the default elogd.cfg file? If you modified the config file and did a mistake there, the program can for example not properly find all directories. Also makse sure you did a full install with "make install", not just update the executable.

Stefan

Roland Beyer wrote:

Hello everybody,

we had to setup a new server for our elog some time ago because the old one crashed. We are now running version ELOG V3.1.1-0767eb0.

In the previous installation we had these nice buttons for file upload, time stamp and equation editor, which are also available here in the online version.

I already found that in the installation directory ("/usr/local/elog/") there exists a directory "scripts" containing a file "ckeditor-config.js", which also contains the lines:
"config.extraPlugins = 'timestamp,dndfiles,eqneditor,fileupload';" and "{ name: 'insert', items: [ 'Image', 'Table', 'HorizontalRule', 'Smiley', 'SpecialChar', 'PageBreak', 'FileUpload', 'Timestamp', 'EqnEditor' ] },"

These plugins seem to be available in the subdirectory "scripts/ckeditor/plugins/". But why are they not loaded? Is it just a version issue? Or something else?

It would be nice to get a hint.

Best regards,

Roland

 

  68856   Sat Oct 27 10:51:12 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxELOG V3.1.2-bd7Re: messy code for chinese charactor
Can you post a screenshot?


Wenhao Huang wrote:
The Chinese character appears messy code. The encoding way is the default utf-8. How can I solve this problem?
  68860   Tue Nov 27 08:59:45 2018 Reply Stefan Rittstefan.ritt@psi.chRequestWindows3.1.2Re: Need to change port 25

I believe Yanick means the SMTP port, not the port under which elogd is listening. The SMPT port is hard wired to 25, because port 587 was not yet defiend when I wrote that code. I can make this a variable, but only if it works. So Yanick can you test if port 587 accepts normal SMTP commands? We don't have such a new server at our lab and I cannot test it. Under Windows you can open a command prompt and telnet to the mail server:

telnet <server> 587
HELO test
MAIL FROM: test

your server should then reply with "220 ..." and "250 ..." messages. Once this works, I will implement the variable SMTP port.

Stefan

Andreas Luedeke wrote:

This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global

The following options are specific to the [global] section:
Port = <port>
Specifies the TCP port under which the server is listening. Default is 80. Can be superseeded via the '-p' command line flag.
Yanick Vachon wrote:

Hi,

We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?

Thanks

 

 

  68863   Wed Nov 28 09:26:11 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows3.1.2Re: French Language

I just tried myself with the current version 3.1.4 and it worked for me flawlessly. Maybe you want to upgrade.

Stefan

Yanick Vachon wrote:

Hi,

When i set Language = French in global config it works in french until i logout, after i can't login anymore, even if i enter my user and password i always stay at the login window, the only way to login again is to edit the Elogd.cfg file in Elog directory, remove the Language = french and save then i can login in and work normally in english version.

 

Thanks.

 

Goto page Previous  1, 2, 3 ... 316, 317, 318 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6