• 0

ESET Internet Security: The ESET LiveGrid® servers cannot be reached


Question

On two computer with ESET Internet Security installed (v 16.1.14.0) I get the  message: The ESET LiveGrid® servers cannot be reached.

Some time stamps [it's mostly on computer 1] - derived from my eset.com account its Activity feed:

Computer 1:
6:00 PM, 05/11/2023
The ESET LiveGrid® servers cannot be reached
7:42 PM, 05/10/2023
4:10 PM, 05/04/2023
1:00 PM, 05/02/2023
9:22 AM, 05/02/2023
8:06 PM, 04/25/2023

Computer 2:
12:05 PM, 05/02/2023
The ESET LiveGrid® servers cannot be reached
10:47 AM, 05/02/2023

What can be the issue here? Is a reinstall an option, or is this ESET related?

14 answers to this question

Recommended Posts

  • 0

I get the live grid not working as well. It's all to do with server addresses not being reached. I ignore it, it works anyway and can be reached eventually. Does not seem to effect the program working. I think it's the ISP.

  • 0

As @NinjaGingeralso mentions, I get this when first booting up and my VPN is taking a moment to connect. I ignore it for 5 minutes, and the problem solves itself.

But maybe our resident guru, @goretskycould offer some tips?

  • 0
On 11/05/2023 at 21:07, Nick H. said:

As @NinjaGingeralso mentions, I get this when first booting up and my VPN is taking a moment to connect. I ignore it for 5 minutes, and the problem solves itself.

But maybe our resident guru, @goretskycould offer some tips?

Strange I can't read the users in your post they're completely white, forum bug? 

  • 0
On 12/05/2023 at 04:55, kiddingguy said:

It's not only when booting up.

Sometimes also after waking up/idle/hibernate.

A reboot though fixed the problem, but that's just a temp solution.

Hi !

I used to have the same issue with ESET, even one of their technicians who took over my computer was never able to fix this annoying problem. He simply stopped troubleshooting and told me it was an application incompatibility, and closed the incident! just like that 😲!

That's why I ditched ESET!

 

  • 0

Hello,

From looking at https://status.eset.com/, it looks like there were issues with ESET's cloud between May 11 12:19 UTC and May 12 13:00 UTC.

The issue with connectivity after a hibernate/sleep/low power state sounds unrelated.  As a complete guess, it sounds like the software isn't detecting or getting the link state info refreshed from the network stack, but, again, that's a complete guess on my part.  I will ask a friend I know over there who's on the core architecture team (which may not be the right person, but it's a starting point), but you may also want to ask in their support forum—the support engineers there  are senior ones who work for ESET's headquarters.

Regards,

Aryeh Goretsky


 

  • 0
On 12/05/2023 at 07:03, goretsky said:

From looking at https://status.eset.com/, it looks like there were issues with ESET's cloud between May 11 12:19 UTC and May 12 13:00 UTC.

Hi!

I encountered this problem long before the period you mention, the problem appeared following an update of the app.

Now I'm using another antivirus, and there is no problem of connection with the database of this one, and no incompatibility with another application. The problem was ESET!

With the experience I had with the support, I will never recommend this security suite. The service completely sucks!

  • 0

Hello,

@snowy owl, I was replying to the person who was having the issue, but thanks for sharing.  I am glad you found something that meets your needs.



@kiddingguy, if you are consistently able to reproduce the problem, ESET's support folks can help you troubleshoot it.  There's are all sorts of detailed logging options for troubleshooting under Advanced setup [F5 key] → Tools → Diagnostics → Advanced Logging, but you would want to speak with a support engineer first to determine what sort of information needs to be captured.

 

Regards,

Aryeh Goretsky
 

  • 0
On 14/05/2023 at 01:04, goretsky said:

I am glad you found something that meets your needs.

Hi,

Indeed, I went back to Kaspersky, which hasn't given me all these problems that I had encountered with ESET.

I also mention the experience I had with one of their technicians who had passed on the incident to a higher level technician. To whom I had sent all the diagnostics of the app, only to be told that there must be some incompatibility with another application, but he could not tell me which one! And with a snap of the finger he closed the request, and then I was on my own. So I can't give any good feedback about them.

Earlier I mentioned that this problem had started after an update of the app, to be more precise, this problem had started around the middle of November 2022, and was happening every day, and then, sometimes the connection ended up being restored the same day or sometimes only the next day.

Good continuation, I will not interfere in your subject anymore.

Have a nice day

Best regards

Edited by snowy owl
misspelling
  • 0

@goretsky

Hi Aryeh,

Just came to my attention about your distinguished career in the AV industry, going back to working with John McAfee at his kitchen table!
John would've been an interesting guy to work with. "If I suicide myself, I didn't. I was whackd." and yet his cause of death is reported as a hanging. 
Was an intriguing story, no doubt.

  • 0

Hello,

Mr. McAfee was certainly an interesting individual; he had an amazing ability to synthesize information from many disparate sources at once and then make a decision.  In retrospect, some of them were wrong, but often they were correct.  He also had an ability to rapidly pivot if something wasn't working out.  These were definitely important skills that allowed him to flourish.

That said, he had grown accustomed to having his way and getting whatever he wanted in the years since he had made his fortune, and was very proud of the control he had over everything around him.  Being jailed and fighting extradition meant having all of that all taken away from him.  At his final extradition you could hear the stress in his voice--he clearly was dreading what was to come next.  I think that what he did was simply his final way of exerting some control over his life.

Regards,

Aryeh Goretsky
 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!