Peter Randziak

Thanks Peter.  Looking forward to when I can beta test the EES for use with Protect Cloud.
Cheers!

Hello Jim / @Trooper,
as of now it is compatible with the on-prem deployment only 😞 (the ESET Bridge management, cert distribution for https caching)
It can be deployed as a stand-alone, not managed proxy for the current endpoints as well.
Peter

Thank you - support have provided me with the updated plugin and initial impressions suggest that the issue is resolved, but I will continue to test.

Hello @obee,
In an unmanaged environment, when the ESET Bridge is installed as a standalone application, not with the EP All-in-one installer, certificates will need to be deployed manually from ESET Protect via policies to have the HTTPS caching working. More information can be found here: https://help.eset.com/ebe/1/en-US/installation.html?caching_https.html
The behavior described above can be reproduced if the HTTPS caching option is enabled in Bridge policy but there was no certificate provided in the policy screen.
Regarding the second question, the cache path provided is correct.
Also the cache.log file from the nginx/logs folder can be inspected for MISS or HIT tags to check whether the data was fetched from the cache or from the upstream servers.
Hope it helps!
Ingemar

For anyone interested in trying ESET Bridge BETA (new solution for ESET traffic caching and forwarding), we have good news to share - we have just released it.
To find out the details and take part, visit the dedicated BETA forum section at https://forum.eset.com/topic/33619-eset-bridge-beta-new-solution-for-eset-traffic-caching-and-forwarding/
 
 

We are delighted to announce the launch of the ESET Bridge BETA program.
 
ESET Bridge is a new solution for caching and forwarding traffic of ESET products heading to ESET's online services.
ESET Bridge, built on NGINX, is a successor of the HTTP Proxy.
To name some of the new features and improvements:
Integration with ESET PROTECT which will allow users to manage ESET Bridge HTTPS traffic caching Certificates deployment via ESET PROTECT Watchdog functionality Crash dump functionality To test the mentioned features, it is required to deploy:
ESET PROTECT BETA build  ESET Bridge BETA build Endpoint 10 BETA build These installation binaries are available at https://forum.eset.com/files/category/9-eset-bridge-beta/
 
Supported OSes for ESET Bridge are Windows Server 2016/2019/2022 and Linux - Linux systems compatible with ESET PROTECT 9.1 Server component
 
Detailed ESET Bridge help is available at https://help.eset.com/ebe/1/en-US/
 
As usually, by downloading and using the builds, you agree with our BETA program agreement, which is available at https://forum.eset.com/files/file/58-eset-beta-program-agreement/

To ask a question or report any issues, you encounter during the BETA just post a reply here.
 
We are looking forward to your participation and feedback,
Peter on behalf of the teams involved

We are delighted to announce the launch of the ESET Bridge BETA program.
 
ESET Bridge is a new solution for caching and forwarding traffic of ESET products heading to ESET's online services.
ESET Bridge, built on NGINX, is a successor of the HTTP Proxy.
To name some of the new features and improvements:
Integration with ESET PROTECT which will allow users to manage ESET Bridge HTTPS traffic caching Certificates deployment via ESET PROTECT Watchdog functionality Crash dump functionality To test the mentioned features, it is required to deploy:
ESET PROTECT BETA build  ESET Bridge BETA build Endpoint 10 BETA build These installation binaries are available at https://forum.eset.com/files/category/9-eset-bridge-beta/
 
Supported OSes for ESET Bridge are Windows Server 2016/2019/2022 and Linux - Linux systems compatible with ESET PROTECT 9.1 Server component
 
Detailed ESET Bridge help is available at https://help.eset.com/ebe/1/en-US/
 
As usually, by downloading and using the builds, you agree with our BETA program agreement, which is available at https://forum.eset.com/files/file/58-eset-beta-program-agreement/

To ask a question or report any issues, you encounter during the BETA just post a reply here.
 
We are looking forward to your participation and feedback,
Peter on behalf of the teams involved

We are delighted to announce the launch of the ESET Bridge BETA program.
 
ESET Bridge is a new solution for caching and forwarding traffic of ESET products heading to ESET's online services.
ESET Bridge, built on NGINX, is a successor of the HTTP Proxy.
To name some of the new features and improvements:
Integration with ESET PROTECT which will allow users to manage ESET Bridge HTTPS traffic caching Certificates deployment via ESET PROTECT Watchdog functionality Crash dump functionality To test the mentioned features, it is required to deploy:
ESET PROTECT BETA build  ESET Bridge BETA build Endpoint 10 BETA build These installation binaries are available at https://forum.eset.com/files/category/9-eset-bridge-beta/
 
Supported OSes for ESET Bridge are Windows Server 2016/2019/2022 and Linux - Linux systems compatible with ESET PROTECT 9.1 Server component
 
Detailed ESET Bridge help is available at https://help.eset.com/ebe/1/en-US/
 
As usually, by downloading and using the builds, you agree with our BETA program agreement, which is available at https://forum.eset.com/files/file/58-eset-beta-program-agreement/

To ask a question or report any issues, you encounter during the BETA just post a reply here.
 
We are looking forward to your participation and feedback,
Peter on behalf of the teams involved

Hello @mathisbilgi
The Apache based HTTP proxy will be completely replaced in the future ESET PROTECT releases.
Stay tuned for BETA, which might appear in a foreseeable future...
Peter

Endpoint 9.0.2046 is currently the latest available via automatic updates. Automatic update to Endpoint v9.1 should be available later this year. If you want to update Endpoint immediately, send a software install task with Endpoint 9.1.2057 to clients. However, I'd recommend testing upgrade only on a smaller group of machines and update the others with a delay.

Hi. For now, I would recommend to just stay on versions that do work for you. Indication was added to notify especially of "Windows" users which tend to use old and unmaintained versions of those components. We will probably have to target this in next release and possibly modify communication in a way that it is supposed to recommend specific component versions for the future.

Regarding Java versions, officially only LTS versions are supported, as other versions are very short-living and tend to introduce breaking changes. We do expect that version 17 will be supported by ESET PROTECT for a longer time. But as of now, from technical perspective, console is still compatible with v8 (but this will probably change in near future).

Hello @safety,
which update server has the customer set?
Does the offline license file contain the username and password?
Can you send me the offline license file via a private message to check?
Peter

ESET's updates contain smart detections that are a few bytes in size, meaning that one detection that describes a particular malicious behavior or malware file characteristics can cover even thousands of variants in an ideal scenario. These are distributed either via pico updates or aggregated in engine updates together with other detections.  Engine updates are optimized for distribution as differential updates.
Currently if only the engine was updated and a computer would be online 24x7, it would download engine updates 6 times a day, each about 11kB in size. If you missed 1 update, you'd download 15,5 kB. If 3 updates were missed, then a 21,4 kB engine would be downloaded, etc. ESET uses modular architecture, meaning that a particular feature can be often released (fixed, improved) via module updates instead of releasing a new version of the program. There are currently about 50 modules (archive module, HIPS module, fw module,...) which are updated more or less frequently depending on the needs.

Thank you @Minimalistand @Marcos for this quesion and answer session.  I posted about this on the forums here a few years ago but did not find a resolution.  Happy to see it is an easy fix.
Cheers.

This will be fixed in the forthcoming service release of Endpoint v9.1 which should be available soon.

Please check your private message.

Hello @tbsky,
can you please provide exact URL you tried to access and also IP of the server?
Peter

Yes, you are right. This behavior is considered to be a bug, and should be fixed in the future versions. To update the agent on the machine where the ESET PROTECT Server is running, you need to  install it either manually (download the standalone MSI) or using the All in One Installer as pointed out above. 

Hello, the "until version 9 + 3 years" applies to version 8 as a whole (8.0, 8.1, etc...), meaning the latest build of version 8 will be supported for that long.
Given there was no version 8.1 at that time, the timeframe was listed with the latest available version (8.0). When 8.1 was released, it "inherited" the "until version 9 + 3 years"  support window.
Technically, it should have said just 8, apologies for that, I can see how that could have been confusing.
It needs to be pointed out, though, that according to https://support-eol.eset.com/en/policy_business/versioning_rules.html, differences between versions 8.0 and 8.1 only consist of bug fixes and minor changes, so a customer may freely and safely upgrade to the latest build within the major version 8 (for which the "until version 9 + 3 years" policy applies) without any significant functionality changes.
With all this being said, we do understand this may not be absolutely clear and easy to understand and, as Marcos already said, a new EOL policy is being prepared, under which every build will have a clearly defined support timeframe already at the time of release.

Problem has been resolved, in our case after migrate to new serwer default policy was turn on and enable proxy serwer with wrong IP. After truning off proxy serwer in policy ELGA starts working.

To explain more about the support for version 8 from the point of view of the EOL policy:
The EOL policy for products in category A states that "Full Support is granted to the latest release of the latest major version and the latest release of the earlier major generation (for only one year after the release of a new product generation)."
When verison 9.0 was released, full support end date for version 8.1, as the latest release of the earlier major generation, was set to one year from this release (November 2022) and the end of limited support was set to three years from this release (November 2024).
 
EOL policy also states: "Limited Support is available for the earlier releases of the latest major product version (one additional year after the next generation comes out) and the latest release of the previous product generation (two additional years after the one year of Full Support has expired)."
 
Version 8.0, as the earlier release of the latest major product version, transitioned to limited support at the time of version 8.1 release, ad its limited support end date was set when version 9.0 came out to one year from version 9.0 release (November 2022).
 
Therefore, version 8 is technically supported until November 2024 in general, as version 8.1 is in limited support until this date. However, what was possibly misleading for you and what we are sorry for is that by the time of your purchase, the EOL policy for version 8.0 showed "Limited Support Until version 9 + 3 years". This was true for version 8 in general, but not exactly for 8.0 after version 8.1 was released. As already mentioned, we are working on improving the accuracy of this communication and setting the rules more transparently.

Thank you for your valuable feedback. We realize that the current EOL policy description may not be clear to end users who expect to know for how long a particular version will continue to receive full and limited support at a specific moment in time. We've been working hard on improving the communication towards our users on this matter. Some minor improvements will be done this year with a bigger overhaul to come in 23H1 which should make the EOL policy perfectly clear.
Let's say you purchased ESET on January 2021. Endpoint v8 was released on December 9, 2020. At this point you'd get full support until v9.0 is released (plus one year) which happens approximately in June (we plan to better communicate the roadmap for new users). According to https://support-eol.eset.com/en/policy_business/support_policy_cat_a.html:
Full Support is granted to the latest release of the latest major version and the latest release of the earlier major generation (for only one year after the release of a new product generation).
Version 8.1 was released on June 15, 2021 and v9.0 on November 30, 2021. From the above statement we infer that full support for the major version 8.1 would last until November 30, 2022, with limited support to end 2 years after the release of v9.0, ie. on November 30, 2024:

 

Hello @eclipse79,
I would recommend to post it to the "Future changes to ESET PROTECT Cloud" topic https://forum.eset.com/topic/25742-future-changes-to-eset-protect-cloud/
As far as I know it is monitored by the responsible people
Peter

Thanks you, I will send you the files

It's a false positive. A new update is being prepared which will address it. We apologize for the inconvenience.