PCS70

Hello, I have multiple Linux machines in my ESET Protect inventory (running either CentOS or Ubuntu).
I have noticed, that machines running Ubuntu doesn't report that there are updates available for operating system (updated packages).
But machines running CentOS, where packages also need to be updated, it shows "Operating system is not up to date" in ESET Protect Web Console.
I want to see this alert on my Ubuntu machines too.
Is there something wrong with configuration or something else? Because everything else works (Running tasks, doing reboots, hardware reports, etc.)

Hello guys,
 
Let me share few findings of our support and dev teams on this with you.
Endpoint 9 started to use EPNS instead of DNS requests to check for license changes. Endpoints 8 and below didn’t report an issue if this check failed.  
When it comes to issues reported on ESET PROTECT Virtual appliance
The issue seems to be the default setting of the following module "reqtimeout_module" which is used/loaded only on VA (this module provides a way to set timeouts and minimum data rates for receiving requests).
 The issue should not be present on the Windows version of the Apache HTTP PROXY because this module is not loaded there.
The workaround could be (1) disabling this module on the VA or (2) setting the appropriate values. We are not sure what is the preferred way and how it might affect other services, as it was not fully tested yet.

To disable limits (i.e. "(2) setting the appropriate values"):
set "RequestReadTimeout header=0 body=0"
in the newly created(in /etc/httpd/conf.d/) configuration file "reqtimeout.conf" with settings mentioned above
and of course the file has to be included in used configuration "IncludeOptional conf.d/reqtimeout.conf" in the "/etc/httpd/conf/httpd.conf"

We are expecting some official solution in the following days.
 
If the customers do not use the Apache HTTP Proxy on VA, enable the Direct Cloud advanced logging, reproduce the issue, collect the logs by ELC and open a ticket for our support teams to check.
  
The configuration option for App status and Notification of "Eset Push Notification Service server cannot be reached" state will be added (P_EESW-8067) The  "Do not remind me again" from EPNS app status doesn't work issue is tracked to be fixed (P_EESW-8048)  
Regards, Peter
 

To sum it up, the issue may be caused by 2 things:
1, If you use Apache http proxy on Linux - the configuration of the http proxy is incorrect. Please refer to the post above how to fix it. Apache HTTP proxy for Windows is not affected.
2, If you don't use Apache http proxy - the issue is caused by a bug in Endpoint v9 which checks for EPNS connectivity even if checking for license changes via EPNS is disabled, ie. when the interval check is set to "Limited". Solution: change it to Automatic. If you need to have it set to Limited for whatever reason, there will be a fix via an automatic module update within a couple of days. Please use "Automatic" at least temporarily until the new Direct cloud communication module is available.

Hello,
Unfortunately, the "auto update" setting does not work for Endpoints V8, and only for V9+. 
In order to enable "auto updates" for V8, please configure this setting accordingly: 

Also, it is important to remember, that even when the "auto update" is enabled, it does not mean that you will get the newer version immediately after its release. Versions are rolled out over time, starting approx. 1-2 month after the formal release into the repository. 
You can read more info about it here: https://help.eset.com/protect_cloud/en-US/auto_updates.html

I understand keeping ESET products up-to-date is very important, but why not leave it up to the customers who pay for your products to decide when to update their devices?  I always keep my products patched, but I decide when to apply them and schedule reboots.  I don't like it that you apply the updates without admin approval and when I login to ESET PROTECT, I find red alerts all of my devices.  What if you push out an update and two hours later, you find it causes a major problem?  You also said that you have an opt out policy, but I don't think you do.  If you did, you would allow customers to permanently disable auto updates and manage them on their own.  If some customers want to keep your auto update policy enabled, that's fine, but you should allow customers the choice to do enable it or keep it disabled without having to worry about it re-enabling.