Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 11:01:00 2022 
    icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 11:13:09 2022 
       icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 11:17:44 2022 
          icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 11:24:36 2022 
             icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 11:40:59 2022 
                icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 12:36:04 2022 
                   icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 12:38:12 2022 Screenshot_2022-07-19_at_12.37.55.png
                      icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 12:48:42 2022 
                         icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 12:57:37 2022 Screenshot_2022-07-19_at_13.02.19.png
                            icon5.gif   Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Fri Jan 20 14:11:52 2023 
Message ID: 69549     Entry time: Tue Jul 19 12:48:42 2022     In reply to: 69548     Reply to this: 69550
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux  ELOG Version: 3.1.3 
Subject: Re: 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.

ELOG V3.1.5-fe60aaf