ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 708 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 707, 708, 709 ... 804, 805, 806 Next

Wed Sep 15 13:52:59 2021

Bolko Beutner

bolko.beutner@desy.de

Question

Linux | Other

3.1.2

Re: Reverse proxy of Elog using Docker and Nginx?

I have the same problem -- did you find a solution in using the nginx revese proxy with user login?

Andrew Wade wrote:

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.

69791

Sun Apr 28 14:45:22 2024

Re: read-only elog server

Hi,

Could you be more specific? Where do I get the 'Menu commands"?

Thanks,

Bockjoo

Stefan Ritt wrote:

Use

Menu commands = List, Find, Help

to remove all command which let you create or edit entries (New, Reply, Edit, ...)

Then do the same with "List menu commands = ..."

/Stefan

Germano Massullo wrote:

Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.

I tried to search on Elog documentation but I had no success

Thank you and have a nice day

65775

Fri Mar 7 13:44:34 2008

Can I control the content of the Subject on an email notification?

i.e. Can I copy the subject from the elog entry into the email subject?

Thanks,

//Bill

65776

Fri Mar 7 14:09:40 2008

Bill Whiting wrote:

Can I control the content of the Subject on an email notification?

i.e. Can I copy the subject from the elog entry into the email subject?

Thanks,

//Bill

I found the answer in the docs.

In the config file add

Use Email Subject = Added Text: $subject

This results in the e-mail subject being set to "Added Text: elogentry subject line"

Thanks for a great tool!

65803

Tue Apr 1 21:07:39 2008

Bill Qualls

bqualls@newgistics.com

I "upgraded" from v2.6.? to v2.7.3. By "upgrade", I mean "copy all files to a different computer, then run the installer". e-mail messages received from my v2.6 instance look nice. The messages look like HTML tables with blue and green coloring. My v2.7 instance appears to send plain text. But, when I forward the v2.7 message, the nice HTML tables appear again. Is there an e-mail formatting setting that I need to change?

65846

Wed Apr 23 01:55:16 2008

scrollable text section only when viewing a log entry

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

65853

Thu Apr 24 23:52:45 2008

Re: scrollable text section only when viewing a log entry

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only", just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
in the style sheet, added attribute "position:fixed" to the "frame table" section;
in the style sheet, added attribute sections for journal entry content and footer div sections:
1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
2. #footer: text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.

Bill

65870

Tue May 6 21:28:18 2008

Re: scrollable text section only when viewing a log entry

IStefan Ritt wrote:

Bill Pier wrote:

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
in the style sheet, added attribute "position:fixed" to the "frame table" section;
in the style sheet, added attribute sections for journal entry content and footer div sections:
1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
2. #footer: text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously. I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

Attachment 1: elog-test.html

Attachment 2: elog-test.css

/* default formatting */
body {
  margin:3px;
  color:black;
  background-color:white;
  font-family:trebuc,verdana,tahoma,sans-serif;
  /* background-image:url(elog.gif); */
}

/* standard link colors and decorations */
a:link { color:#0000FF; text-decoration:none }
a:visited { color:#800080; text-decoration:none }
a:hover { color:#0000FF; text-decoration:underline }
a:active { color:#0000FF; text-decoration:underline }
a:focus { color:#0000FF; text-decoration:underline }

td {
  color:black;
  font-size:14px;
}

/* frame table */
.frame {
  width:100%;position:fixed;
}

/* printable frame table */
.pframe {
  width:600px;
}

/* standard formatting for logbook tabs */
.tabs {
  font-family:sans-serif;
  font-size:12pt;
  background-color:white;
}

/* logbook selection page */
.selframe {
  width:60%;
  background-color:#486090; 
  border:1px solid #486090;
  font-size:14pt;
}

.seltitle {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  color:#486090;
  text-align:center;
}

.selexp {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  color:#486090;
  text-align:left;
  font-size:10pt;
}

.selspace {
  width:2%;
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#EEEEEE;
}

.selgroup {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#FFCCFF;
  padding:3px;
  text-align:left;
  font-weight:bold;
  font-size:14pt;
}

.sellogbook {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  padding:3px;
  text-align:left;
  font-weight:bold;
}

.selcomment {
  font-size:10pt;
}

.selentries {
  background-color:#E0E0A0;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  text-align:center;
  font-size:12pt;
}

/* unselected and selected group tabs */

.gtab a {
  background-color:#B0E0B0;
  padding-left:5px;
  padding-right:5px;
}

.gtab {
  background-color:#B0E0B0;
  border-right:1px solid #409040;
}

.sgtab a {
  color:white;
  padding-left:5px;
  padding-right:5px;
}

.sgtab {
  background-color:#486090;
  color:white;
  border-right:1px solid #084070;
}

.sgtab a:visited { color:white; } /* bug for IE */

/* unselected and selected logbook tabs */

.ltab a {
  background-color:#E0E0E0;
  padding-left:5px;
  padding-right:5px;
}

.ltab {
  background-color:#E0E0E0;
  border-top:1px solid white;
  border-left:1px solid white;
  border-right:1px solid gray;
}

.sltab a {
  background-color:#486090;
  color:white;
  padding-left:5px;
  padding-right:5px;
}

.sltab {
  background-color:#486090;
  color:white;
  border-left:1px solid #E0E0E0;
  border-right:1px solid #084070;
}

.sltab a:visited { color:white; } /* bug for IE */

/* logbook title, left, middle and right cell */

.title1 {
  padding:5px;
  background-color:#486090;
  border-bottom:1px solid black;
  border-left:1px solid #E0E0E0;
  color:white;
  font-size:medium;
  font-family:sans-serif;
  text-align:left;
}

.title1 a:visited { color:#A0FFA0; }
.title1 a:link { color:#A0FFA0; }

.title2 {
  background-color:#486090;
  border-bottom:1px solid black;
  color:white;
  font-size:medium;
  font-family:sans-serif;
  text-align:center;
}

.title3 {
  border-bottom:1px solid black;
  border-right:1px solid black;
  background-color:#486090;
  text-align:right;
  width:100px;
}

/* main menu row */

.menuframe {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
}

.menu1 {
  text-align:left;
  font-size:12pt;
}

.menu1a {
  text-align:right;
  font-size:10pt;
  font-weight:bold;
}

.menu2a {
  text-align:left;
  font-size:10pt;
}

.menu2b {
  text-align:right;
  font-size:10pt;
}

.menu3 {
  text-align:left;
  font-size:8pt;
  font-weight:bold;
}

.menu4 {
  text-align:right;
  font-size:10pt;
  vertical-align:middle;
}

.menucenter {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
  text-align:center;
  font-size:10pt;
}

.toolframe {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
  padding:2px;
}

/* frame table in listings */
.listframe {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1pc solid white;
  background-color:#486090;
  border:0px;
}

/* title row in listing */
.listtitle {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  text-align:center;
}

/* odd and even lines in message listing */

.list1 {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  text-align:center;
}

.list2 {
  border:1px solid #808040;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#FFFFB0;
  text-align:center;
}

.list1h {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  text-align:center;
  font-weight:bold;

... 360 more lines ...

Attachment 3: last.png

Attachment 4: first.png

Attachment 5: elog.png

Attachment 6: previous.png

Attachment 7: next.png

Goto page Previous 1, 2, 3 ... 707, 708, 709 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6