IggyPop

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

Hi @IggyPop
Thank you, now the error is gone and my eset-bridge looks normal.
still exploring this bridge, thank you again.
 

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

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

Got it. Will further check with customer support thanks! @IggyPop

Thank you for your response Ingermar. I will create a support ticket.

May I know the steps to migrate ESA from installed server to a new server

Release Date: February 1, 2022
ESET Secure Authentication version 3.0.61.0 has been released and is available to download.
Changelog:
Version 3.0.61.0
Fixed: Port availability prerequisite fails.
Fixed: Do not use PowerShell in Elasticsearch setup.
Fixed: AD FS managed service account incorrectly cut to 15 characters.
Fixed: Implement parallel DNS requests.
Fixed: FIDO - allowCredentials - inconsistency between core and Windows Login.
  Support Resources
ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support.
Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

Hi @IggyPop
Did that.  Seems as if it has been delegated to the back-end team per the engineer I was working with.
Thanks!

Hi Tropper,
not sure why this would be happening I would recommend you contact Support and they will investigate this with you. This is the best way how to resolve this issue in my opinion.
So please feel free to contact them.
Thanks!

Hi there,
based on your information please see below the recommendation: 

You can also find more information about your inquire on this link.
Kind regards,
Ingemar

Hi @j-gray,
One question are you not using a Datto RMM within your environment?
Thanks.
Ingemar

Hey Kamil,
As Peter has mentioned please visit the page where it is all covered with a recommendation from the Development Team. However, meanwhile we are preparing a hotfix for this vulnerability and it should be available this week.
Thanks,
Iggy

Hello @DerKamil,
I recommend to check https://support.eset.com/en/kb8190-vulnerability-log4j2-in-the-reporting-engine-elasticsearch-of-eset-secure-authentication 
The KB article covers Vulnerability log4j2 in the Reporting Engine (Elasticsearch) of ESET Secure Authentication
Peter

I use it has hard token, not Fido