Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 12:48:42 2022
|
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. |
Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Tue Jul 19 12:57:37 2022 
|
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 |
Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Fri Jan 20 14:08:25 2023
|
The issue is still present and now it's quite urgent to move this last service into the Swarm. Does anyone maybe have an idea what's wrong? To
sum up: if there is a non-empty password file, the login page chokes in an infinite loop of redirects. I am using the same HAProxy load balancer configuration
as for all the other services (running Apache, NGINX, GitLab, XWiki, etc.): |
|
Re: Too many redirects when running behind load balancer?, posted by Tamas Gal on Fri Jan 20 14:11:52 2023
|
The issue is still present and now it's quite urgent to move this last service into the Swarm. Does anyone maybe have an idea what's wrong? To
sum up: if there is a non-empty password file, the login page chokes in an infinite loop of redirects. I am using the same HAProxy load balancer configuration
as for all the other services (running Apache, NGINX, GitLab, XWiki, etc.): |
|
ssl certificate, posted by Giuseppe Cucinotta on Wed Jan 25 17:41:30 2023
|
We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing
the older server.crt
The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore. |
|
Re: ssl certificate, posted by Laurent Jean-Rigaud on Wed Jan 25 21:44:51 2023
|
Hi Giuseppe,
The new certificate files should be copy under ssl folder (/usr/local/elog/ssl or /usr/share/elog/ssl by example, closed to templates and script
directories) in place of the embedded (autosigned) certificate files enclosed with ELOG source. |
|
Re: ssl certificate, posted by Giuseppe Cucinotta on Wed Jan 25 22:22:07 2023
|
Hi Laurent,
thanks very much! Probably I've copied the certificate in the wrong directory. I'll try ASAP
Laurent |
|
Re: ssl certificate, posted by Giuseppe Cucinotta on Fri Feb 17 14:29:54 2023
|
Hi I'm here again,
According to my conf file I run elog under a specified user and group different from root. So I copied the .pem file I obtained
from certbot in /etc/ssl as well as /urs/local/elog/ssl and ssl folder in the user directory (I will call it <user-dir>) but when |