Jump to content

serpher

Members
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

Kudos

1 Novice Reputation badge

See kudos

About serpher

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Australia
  1.    BlueBear reacted to a post in a topic: Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
  2. serpher
    There was an update to deb10u10 and that seems to fixed it.
  3. serpher started following ESET Push or LiveGrid cannot be reached , ESET PROTECT Console won't start after tomcat9 update , Run Command Task won't execute on target computer and 2 others
  4. serpher
    The server has updated these packages (security updates): libtomcat9-java from 9.0.31-1~deb10u8 to 9.0.31-1~deb10u9 tomcat9 from 9.0.31-1~deb10u8 to 9.0.31-1~deb10u9 After that the console won't start. Should I downgrade ?
  5. serpher
    One of the Trace Messages is: "Invalid utf8 leading byte" As well as trace.log shows bunch of timeouts. Testing on certain Windows 10 machines with windows firewall turned off it does the same. I wonder if maybe windows updates could cause this. trace.log
  6. serpher
    I'm having trouble with executing commands on remote PC's via ESET PROTECT Console. It says that the task is Running, but it is running forever until timeout or error that could not be executed. It only happens on ~20% of the machines. Any idea what could cause this?
  7. serpher
    Description: More templates Detail: New options to choose from in dynamic templates such as: Computer name, tags, IP address and etc. Pretty much all available columns from Computers section.
  8. serpher
    By "auto-update feature" you mean built-in auto-update policy? I don't really see it work, I can't find if it triggers.
  9. serpher
    Does ESET Endpoint really needs a restart every time there's an (incremental) update or settings are turned on/off? For example going from 10.1.2046 to 10.1.2050 requires a restart. In our workflow, we have some PC stations that are really important/critical to operate. Every PC has to have AV but restarting important PCs is kinda difficult.
  10. serpher
    Additionally I noticed that I can't remove any managed device. Error message just says internal server error.
  11. serpher
    After updating to the newest ESET Bridge 2.0.2.0 it can't connect to anything now causing large CPU and RAM usage. Rebooting doesn't work (Debian 10). 192.168.10.50:3128 is the ESET server. 2023/07/25 21:20:01 [error] 638#0: *6421117 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.10.50 server: , request: "HEAD hxxp://update.eset.com/eset_upd/ep10/dll/update.ver.signed HTTP/1.1", upstream: "hxxp://192.168.10.50:3128/eset_upd/ep10/dll/update.ver.signed", host: "update.eset.com"
  12. serpher
    ESET Log Collector logs (161 MB) https://www.transfernow.net/dl/20230418Rpf51TYG Also, for updates to go though ESET Bridge I assume I have to edit Proxy update settings for Endpoint policy as well ? I don't know if those polices are correct. ESET Bridge 2023-04-18 21-59-57.datESET Managment Agent via ESET Bridge 2023-04-18 22-03-25.dat
  13. serpher
    I have ESET PROTECT with ESET Bridge working and there are some PC's that can't connect to ESET Push notification and/or ESET LiveGrid for some reason. All traffic from ESET server where ESET Bridge is, is not blocked by any means. Vast majority has no problems but some do. ESET Endpoint and Agent is up-to-date. Even if I allow said PC access to the Internet, ESET LiveGrid will still be unavailable. Why is that?
×
×
  • Create New...