Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 729 of 793  Not logged in ELOG logo
ID Date Iconup Author Author Email Category OS ELOG Version Subject
  69546   Tue Jul 19 11:40:59 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: Too many redirects when running behind load balancer?

Yeah, after you enter a password, elog redirects to what it finds in "URL". You can trace that by opening "development tools" in Google Chrome, go to "network" and watch packets going back and forth. I never worked with the load balancer, but maybe you need a different "URL" containing a '/' at the end?

Tamas Gal wrote:

I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes.

 

  69547   Tue Jul 19 12:36:04 2022 Reply Tamas Galtgal@km3net.deQuestionLinux3.1.3Re: Too many redirects when running behind load balancer?

My problem is that I don't even reach the page where I can enter a password. If you go to https://elog.test.km3net.de and click on a logbook, you'll see that it immediately goes into a redirect loop. I already logged the routing but there is nothing else...

Stefan Ritt wrote:

Yeah, after you enter a password, elog redirects to what it finds in "URL". You can trace that by opening "development tools" in Google Chrome, go to "network" and watch packets going back and forth. I never worked with the load balancer, but maybe you need a different "URL" containing a '/' at the end?

Tamas Gal wrote:

I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes.

 

 

  69548   Tue Jul 19 12:38:12 2022 Reply Tamas Galtgal@km3net.deQuestionLinux3.1.3Re: Too many redirects when running behind load balancer?

Attached is the log, where you can see that `Operations+IT` redirects to `Operations+IT/` and that redirects to `Operations+IT` again, which then goes to `elog.test.km3net.de` and `Operations+IT` again etc. etc.

EDIT: I  use the very same load balancer confugration for dozens of other services incl. Apache, Nginx, GitLab, Mattermost, RocketChat etc. and all work fine. As written before, also the "example" logbook works (without password protection).

I also tried `/` at the end of the URL but it has no effect.

I am pretty clueless currently...

Attachment 1: Screenshot_2022-07-19_at_12.37.55.png
Screenshot_2022-07-19_at_12.37.55.png
  69549   Tue Jul 19 12:48:42 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: Too many redirects when running behind load balancer?

Yes I see the redirects. You say with the example logbook it works, right? Is it the password protection which triggers the problem or anything else? Does it work if you take out the password protection? The key is to identify which setting in your config file triggers the problem, so you can bracket the problem down between the example logbook and your logbook definition.

  69550   Tue Jul 19 12:57:37 2022 Reply Tamas Galtgal@km3net.deQuestionLinux3.1.3Re: Too many redirects when running behind load balancer?

Yes, I used the empty `passwd` file from example. When I then click on one of the logbooks, I get to the page where I can register a user (see attached screenshot). After clickin on "Save" for the user registration, I again get the redirect error. Once there is a registered user (i.e. a non-empty password file) the redirect issue is persistent. Any idea where the problem might be? I just emptied the password file again, so you can have a one-shot, if you like.

Btw. I have SSL termination in the load balancer, so ELOG does not need to do any SSL related things (the swarm is in a locally isolated network, so all internal communication between the load balancer and the swarm machines are safe). Maybe that's the issue? On the other hand, the main page loads fine and uses SSL termination too, so I don't know, maybe there is logic behind the authentication which collides with the SSL termination.

Stefan Ritt wrote:

Yes I see the redirects. You say with the example logbook it works, right? Is it the password protection which triggers the problem or anything else? Does it work if you take out the password protection? The key is to identify which setting in your config file triggers the problem, so you can bracket the problem down between the example logbook and your logbook definition.

 

Attachment 1: Screenshot_2022-07-19_at_13.02.19.png
Screenshot_2022-07-19_at_13.02.19.png
  69551   Fri Jul 29 14:22:00 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX3.1.4Re: OSX Issues

I just tried the same on my latpop (MacOSX 12.4) and it worked flawlessly:

ritt@MBP14 build % echo "blah" | ./elog -h 127.0.0.1 -p 8080 -l demo -r 2 -x
Message successfully transmitted, ID=3
ritt@MBP14 build % host 127.0.0.1
Host 1.0.0.127.in-addr.arpa. not found: 3(NXDOMAIN)
ritt@MBP14 build % echo "blah" | ./elog -h localhost -p 8080 -l demo -r 2 -x
Message successfully transmitted, ID=4
ritt@MBP14 build %

So have you tried with the "-v" flag? Maybe your network is not correctly configured. You can also try the "curl" utility (see elog:68597), maybe you see some different error there. You get that via MacPorts.

Stefan

 

  69553   Mon Aug 8 08:26:11 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.4-2Re: Unable to add user
I recommend to clear all your browser cookies for the elog server. Sometimes an old cookie confuses the
access mechanism.

Stefan
  69554   Mon Aug 8 14:06:28 2022 Reply Uwe Vollbrachtuwe.vollbracht@malteser-bergheim.deQuestionWindows3.1.4-2Re: Unable to add user
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
ELOG V3.1.5-fe60aaf