john_White24778

Many Isolated Servers are activated with legacy Offline License and they did not need firewall module to be activated. these servers will upgrade automatically with offline repository, Is there any issue for these servers ?

We have same problem in many servers ! Why V11 is placed on Automatic Update when it is just released and seem to be not fully tested !

We sent them to distributor but they are working even after 2-3 month . Please check your PM @Marcos

Hi dear ESET staffs How we can report leaked and shared license from fake resellers to ESET , is there any Email address or ... ? We find some business license and send them for @Marcos

Yes We were sure that there is a very public and Bad Bug. We Are waiting for a fix . Thank you for a rapid answer as usual 😘

@Marcos Today I Checked over 5 ESET Protect Console and All of them has same issue

please Add an IP and Click SAVE.

Hi Dear @Marcos It Seems that there is a bug in new Console Module Update and it is happening in all ESET Protect . Why Should i raise a support ticket for such a general bug ! Is there any direct Email Address for Quick Support ? Support form at ESET website is not a quick solution.

Update module 1036 (20230731) Translation support module 1986 (20231003) SysInspector module 1283 (20220614) SSL module 1081B (20230905) Push Notification Service module 1134 (20231005) Configuration module 2092.2 (20230929) We Test that this error occurred even in V9 Console !

Hi dears From today When we want to EDIT IPSet section in Endpoint Security policy , Web Console will Show This Error and we can not EDIT Or Update Policy : Something went wrong... *version: 10.1.277.0* *locale: en_US* *user.agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0 (gecko1_8)* *document: https://192.168.1.27/era/webconsole/B2D1F71FD22B49AAFA6C259B9A28273B.cache.html* *url: https://192.168.1.27/era/webconsole/#id=POLICIES:id=EDIT_POLICIES;prod=eset.local.products.endpoint;p=1* *error:* Config engine error: Failed to set values, path Settings.NetworkAccessProtection.IpSets.1.Description status 24 : Read-only value write rejected Product: eset.local.products.endpoint Last loaded screen: features.networkaccess.ipset Last requested screen(s): features.networkaccess.ipset RPC method: _CE.rpc_api.screen_values_set This is our Server Info : ESET PROTECT (Server), Version 10.1 (10.1.1291.0) ESET PROTECT (Web Console), Version 10.1 (10.1.277.0) Name Version Update module 1036 (20230731) Translation support module 1986 (20231003) SysInspector module 1283 (20220614) SSL module 1081B (20230905) Push Notification Service module 1134 (20231005) Configuration module 2092.2 (20230929)

all of them is now blocked . tanx

last two update server that are not accessible via browsers are not blacked yet , you must add their update address to AV to see that they work : *** Edited

Their update servers are work fine and not blocked from updating yet !!! just their domain is blocked via browsers . it is about 21 days that we report these compnaies to ESET , 21 days is not enough ??? Why ESET is so slow in such these cases while illegal companies are increase daily . ESET must black list illigal update servers very quickly so they can not continue their activities.

after 13 days their domain are blocked but their update servers is not black listed and their update server is working find and not blocked yet ...

some of them is blocked via browsers but They not blocked for updating . it is about 10 days that their update servers are working fine and we have not revive any answered from ESET lab.