As any other box esafe comes with some default configs , to much of my surprise it takes too long to find them in the Esafe docs, so here they are:
eConsole TCP port: 43970
eConsole UDP port: 43982
Webmin TCP port: 37233 - https to eSafe, when installed on linux [last eSAfe to support
Windows was eSafe 6 FR2] (https://ip_address_of_esafe:37233)
default username: root
default password: kn1TG7psLu
Webmin username: admin
Webmin password: esafe
econsole default username: admin
econsole default pasword: no such, you will be asked to set on first login or during Webmin configuration
————————————————————————–
Product Configuration file:
/opt/eSafe/eSafeCR/esafecfg.ini
Nitroinspection Configuration file:
/opt/eSafe/esafenipca.ini
eSafe Machine Configuration file:
/opt/eSafe/esafe.ini
eSafe Applifilter Configuration file:
/opt/eSafe/eSafeCR/applifilter2.ini
————————————————————————–
Spool Directory:
/opt/eSafe/eSafeCR/SPOOL/
Advanced antispam and URL filtering (cobion) database Directory:
/var/esafe/ofdb/
Session log files:
/opt/eSafe/eSafeCR/SessionLog/
Machine logs – when debug mode enabled logs get written here:
/var/esafe/log/eSafeCR
Debugging procedure , quite standard procedure, provided load on the machine permits
(High Debug mode loads the machine a lot!) you may shorten the time of troubleshooting
when opening ticket in Aladdin.
You need to re-create the problem first in high debug level (you can do it with eConsole: Options > Troubleshooting… > Clear Log Files > choose High troubleshooting level > re-create the problem > choose “Off” to turn off troubleshooting level)
How to create support file:
cd /opt/eSafe
./esafeinf
Collecting eSafe info and log files, Please wait …
Information successfully logged in
/var/log/1004562_xxxxxxx3430esglog.tar.gz.
or:
enter Webmin (https://ip_address_of_esafe:37233) > Support > Create and download eSafe Support Info file
————————————————————————–
eSafe Machine configuration script (script has same functionality as Webmin does):
cd /opt/eSafe
./esgmenu
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.