Jump to content

The ESET LiveGrid servers cannot be reached


Recommended Posts

I have this message on and off for the past 4-6 months.

Only on 1 device though. Other devices I run ESET on don't have this issue.
It's not OS dependent, because at least in two cases each notebook has Windows 11 23H2 installed [one with this error, the other not].
The message pops up mostly when it's coming out of idle stage. And sometimes a (simple) restart will also do [though not how it should be]

It happend with different (sub)versions of ESET Internet Security v16.
Now also with ESET Smart Security Premium 17.0.15.0

Any idea what can be the cause of this? 

Link to comment
Share on other sites

  • Administrators

Are you able to reproduce the error at any time, e.g. after a computer restart? Does the machine connect to the Internet directly or through a proxy? Is the machine behind a firewall? Asking since we'll need advanced logs from time shortly before the error is reported.

Link to comment
Share on other sites

This just happened (and not on my other notebook)

Q: Are you able to reproduce the error at any time, e.g. after a computer restart?
A: Only after a (hibernate), relogin in Windows after like 30-60 mins

Q: Does the machine connect to the Internet directly or through a proxy?
A: Directly to internet, no proxy [as far as I know]

Q: Is the machine behind a firewall?
A: Not a hardware-based firewall. Just the ESET application.

 

image.png

Link to comment
Share on other sites

After some time... the Service Servers are being put on/online again and the message disappears [at least after the log collection]. But also after a restart of Windows 11 everything's back to normal.

Link to comment
Share on other sites

  • Administrators

You can upload the logs here since attachments are available only to ESET staff, or upload the archive to a file sharing service and drop me a private message with a download link if it's too big to upload here.

Link to comment
Share on other sites

  • Administrators
1 hour ago, kidding_guy said:

Anything found already in the log files?

I didn't find any errors logged. Perhaps advanced logging was not enabled prior to the network communication issue?

If it takes long for the error to occur, enable just advanced direct cloud logging under Tools -> Diagnostics in the advanced setup. When the error occurs, disable logging and collect logs with ESET Log Collector.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...