Re: Reverse proxy of Elog using Docker and Nginx?, posted by Andrew Wade on Fri Aug 17 22:07:41 2018
|
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.
|
|
|
|
Re: Reverse proxy of Elog using Docker and Nginx?, posted by Stefan Ritt on Mon Aug 20 12:42:24 2018
|
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.
|
|
|
|
|
Re: Reverse proxy of Elog using Docker and Nginx?, posted by Andrew Wade on Tue Aug 28 23:38:55 2018
|
It does indeed seem to be a cookie stripping issue. I just need to figure out how to get Nginx to forward these properly.
Thanks for the help.
| Stefan Ritt wrote: |
|
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.
|
|
|
|
|
Need to change port 25, posted by Yanick Vachon on Mon Nov 26 17:32:31 2018
|
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 |
|
Re: Need to change port 25, posted by Andreas Luedeke on Tue Nov 27 08:19:11 2018
|
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
|
|
|
Re: Need to change port 25, posted by Stefan Ritt on Tue Nov 27 08:59:45 2018
|
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
|
|
|
Re: Need to change port 25, posted by Yanick Vachon on Tue Nov 27 15:21:31 2018 
|
I Stefan, it works with the 587 port.
| Stefan Ritt wrote: |
|
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
|
|
|
|
|
French Language, posted by Yanick Vachon on Tue Nov 27 20:06:17 2018
|
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. |