|
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
| Andreas Luedeke wrote: |
|
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
| |
|
how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|