Marcos

Unfortunately it's not clear what you mean by managing devices. You can manage your licenses via the License manager at my.eset.com. There is also a link to the Anti-Theft portal where you can manage Anti-Theft on mobile phones and notebooks.

We have recently discovered a problem sending customer care requests from the built-in form in ESET NOD32 for Linux desktop. I would recommend contacting ESET LLL via the web form or phone. We are working on a resolution to make the internal form work. We apologize for the inconvenience.

I'm afraid you can't do much about it. You can contact the person and ask for a refund but since the person is from Middle East I'm afraid he or she won't respond to it. We strongly recommend purchasing a license only from authorized sellers and e-shops.

It shouldn't be a problem at runtime since the web access protection can provide the firewall with the hostname that has resolved to the IP address, however, if the hostname was used in a rule at a later time it wouldn't work as expected I assume. Example: You receive an interactive firewall dialog about communication with 216.58.201.78, web access protection would tell the firewall there has been a communication with maps.google.com that resolved to this address recently. A firewall rule would be created for maps.google.com which would, however, internally translate to a firewall rule for the above IP address. Such rule wouldn't work the next time since maps.google.com could resolve to a different IP address from subnet 216.58.201.0/24. Moreover, it could be that you would like to block access to youtube.com that would resolve to an already allowed IP address: Name: youtube.com Addresses: 2a00:1450:4014:800::200e 216.58.201.78 Name: maps.google.com Addresses: 2a00:1450:4014:800::200e 216.58.201.78 As a result, there would be 2 conflicting rules. A permissive rule for 216.58.201.78 and a blocking rule for the same IP address.

I would recommend collecting logs as per the instructions at https://support.eset.com/en/kb3404-use-eset-logcollector-on-macos-and-send-the-logs-to-eset-technical-support and opening a support ticket with your local ESET distributor.

If the mirror is not accessible via http and you update from a share, make sure to configure an account with read or full permissions to the share in the advanced update setup:

Please collect logs as per the instructions at https://support.eset.com/en/kb3404-use-eset-logcollector-on-macos-and-send-the-logs-to-eset-technical-support and open a support ticket with your local ESET distributor.

Does it open automatically in a browser or what is the problem with it? To me it looks legitimate and it's not blocked by ESET.

The detection is actually correct. It was already reported here in the past and obviously an administrator of the website still hasn't removed the references to defpush.com which is why the detection is triggered.

Please provide me with the following stuff for investigation: - logs collected with ESET Log Collector - the content of the "C:\ProgramData\ESET\ESET Security\IPM" folder Unfortunately you didn't mention what ESET product you have. If ESET NOD32 Antivirus, then there is actually a good reason to upgrade at least to ESET Internet Security not because of features like Anti-Theft, Antispam, Parental Control or firewall but mainly because of the Network attack protection which can: - protect your system from RDP, SMB, SQL,...bruteforce attacks (RDP bruteforce attacks are nowadays a common infection vector exploited by attackers to get in, disable AV and run ransomware) - Botnet protection which is a part of it can detect and block malicious communication of malware acting as a bot (useful especially in case of new malware not recognized by other scanners yet in case it manages it to run start to communicate with other bots)

Never seen the error to be caused by missing Windows updates. Do you know what updates must not be installed in order for the error to occur?

Logs need to be provided to customer care that will pass them further to developers. Please create a support ticket with your local ESET distributor.

Normally you should get a warning about untrusted certificate from the browser if a self-signed certificate is used by Tomcat: You should choose to remember the action and click Allow. If you would like me to check your ESET product settings and modules which might affect the display of the interactive window, please provide me with logs collected with ESET Log Collector.

This issue has been discussed in length recently here, please read the red alert on top of this page. For latest information, read https://support.eset.com/en/alert7396-legacy-products-startup-issue or https://support.eset.com/en/kb7442-solution-for-eset-endpoint-product-5x (for Endpoint v5). After fixing the issue, we strongly recommend uninstalling Endpoint v5 and installing the latest Endpoint 7.2 on systems wherever possible, especially if you are using Windows 10 or Windows 7/8 and security of the system matters.

Have you tried uninstalling EIS and installing v13.0.24 from scratch? Is that the latest version 13 that you have currently installed?