Gleen 0 Posted August 31, 2023 Share Posted August 31, 2023 The transmission between the eset bridge and the agent looks normal, there is a request for the version and it is correct then data is sent I have errors such as Bad TCP. And it's not a link problem Link to comment Share on other sites More sharing options...
ma77y88 11 Posted August 31, 2023 Share Posted August 31, 2023 Yes, still not working here. Link to comment Share on other sites More sharing options...
AdWiMa 2 Posted August 31, 2023 Share Posted August 31, 2023 After we cleared the cache of the bridge it now works for us (on-prem). ma77y88 and Arko 2 Link to comment Share on other sites More sharing options...
mkrupa 0 Posted August 31, 2023 Share Posted August 31, 2023 How can you clear the cache? Link to comment Share on other sites More sharing options...
AdWiMa 2 Posted August 31, 2023 Share Posted August 31, 2023 We stopped the ESET Bridge services and then deleted the contents of the cache folder. Link to comment Share on other sites More sharing options...
ma77y88 11 Posted August 31, 2023 Share Posted August 31, 2023 This seems to have worked for us on-prem. Clear C:\ProgramData\ESET\Bridge\Proxies\Nginx\data\eset_cache Link to comment Share on other sites More sharing options...
AdWiMa 2 Posted August 31, 2023 Share Posted August 31, 2023 we have redirected the cache folder to another drive via the bridge policy Link to comment Share on other sites More sharing options...
Gleen 0 Posted August 31, 2023 Share Posted August 31, 2023 I confirm after clearing the cache it works Link to comment Share on other sites More sharing options...
IT-KAV 1 Posted August 31, 2023 Share Posted August 31, 2023 I was able to update test client after cache clearing. But agent on Protect server itself has outdated paramater in Protect and at the same time refuse to update. With message, that there is nothing to update... Link to comment Share on other sites More sharing options...
ESET Staff Solution IggyPop 22 Posted August 31, 2023 ESET Staff Solution Share Posted August 31, 2023 Hi everyone, Based on the information from the ESET Bridge development team this should be resolved. Please just clear the cache and this should resolve the issue. Thanks, Iggy Link to comment Share on other sites More sharing options...
Recommended Posts