Im not running anything on port 443, one thing I did notice is that when 
stunnel is run and setup, I can run a netstat and nothing is bound to those 
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the 
command initially ?


CONFUSED ????

> > I was wondering if you can help me understand the concept and if i am 
doing 
> > something wrong with securing Elog via SSL
> > 
> > Basically im running elog on a redhat 8 box with stunnel already 
installed 
> > as part of OpenSSL, on the server i ran the command specified in the 
> > instructions
> > 
> > stunnel -d 443 -r 172.16.24.108:81
> > 
> > This command runs on the server, but when I access https://172.16.24.108/ 
i 
> > get a page cannot be displayed, ive also put the URL = 
> > https://172.16.24.108 entry in the elogd.cfg file
> > 
> > HELP!!!!!!!
> 
> Can you access your server locally under http://172.16.24.108:81 ??? If 
not, 
> then you maybe specified the wrong port, so check elogd.cfg and the "-p" 
flag 
> when starting elogd. If you can access it, and cannot access it under 
> https://, then something must be wrong with your stunnel configuration. 
Maybe 
> you run already a secure server under port 443? User "netstat -a" to check 
> that.

Ooops, I destroyed the original post, now how can we fix this :)

> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
> 
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81
> 
> This command runs on the server, but when I access https://172.16.24.108/ i 
> get a page cannot be displayed, ive also put the URL = 
> https://172.16.24.108 entry in the elogd.cfg file
> 
> HELP!!!!!!!

Can you access your server locally under http://172.16.24.108:81 ??? If not, 
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag 
when starting elogd. If you can access it, and cannot access it under 
https://, then something must be wrong with your stunnel configuration. Maybe 
you run already a secure server under port 443? User "netstat -a" to check 
that.

> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> > 
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
> 
> If you installed from the RPM, elogd runs under the user "elog". If you have 
> installed a previous version under a different user, it might be that elogd 
> does not have read or write access to it. A 
> 
> "chown -R elog.elog /usr/local/elogdata"
> 
> might help.
>
 
It did, a lot, guess I missed that one in the changelog.

Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked

As a test I changed subdir to it's relative path
restarted
It kept working

mmmm, I wonder where that twighlight tune comes from ...

> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
> 
> Cannot open file /usr/local/elogdata/logbooks/djeks/password!

If you installed from the RPM, elogd runs under the user "elog". If you have 
installed a previous version under a different user, it might be that elogd 
does not have read or write access to it. A 

"chown -R elog.elog /usr/local/elogdata"

might help.

- Stefan

After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.

Cannot open file /usr/local/elogdata/logbooks/djeks/password!

oops?

> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81

I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.

Reference: http://www.tldp.org/linuxfocus/common/sart/index.html

> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> > port bindings, basically im running elog bound to port 81 and when i 
> > install the new RPM it refuses to bind to this port, i tried port 8080 
and 
> > that worked fine

The bug has been fixed in V 2.3.3 which has been released today.