Problem z ESET Push notification Service

[Martino 1]

Dzien dobry,

Jestem tutaj nowy ale mam taki problem ze po aktualizacji z wersji 8 do wersji 9.0 pojawia sie komunikat jak w załączniku. Może temat byl tutaj juz poruszany ale szukałem i nie znalazłem.

nadmienię ze do tej pory było wszystko ok. z wersja 8.1 nic grzebane nie bylo w configu.

[Peter Randziak 1,183]

Hello @Martino,

please see this post by my colleague and follow the steps described in it
https://forum.eset.com/topic/30570-endpoint-security-cant-connect-to-push-notification-service/?do=findComment&comment=143698

 

If you do not use Apache HTTP Proxy on ESET PROTECT / ESMC VA, you may try to switch to pre-release update channel on an affected machine temporarily to see if it resolves the issue.

 

Since this is an English forum, please post in English so understand each other and assist you...
Regards, Peter

 

[Martino 1]

I understand well only I do not have a proxy server. This problem occurred after upgrading to ESET PROTECT Server 9.0.2144.0.
I currently have:
ESET Management Agent 9.0.2141.0
ESET PROTECT Server 9.0.2144.0
ESET Rogue Detection Sensor 1.1.615.1

Edited January 10, 2022 by Martino

[Peter Randziak 1,183]

Hello @Martino,

Direct Cloud communication module 1123.2 has been released today, please check if the system affected has it and if yes, let us know if the issue was resolved by it.

Peter

[Martino 1]

I understand well only I do not have a proxy server. This problem occurred after upgrading to ESET PROTECT Server 9.0.2144.0.
I currently have:
ESET Management Agent 9.0.2141.0
ESET PROTECT Server 9.0.2144.0
ESET Rogue Detection Sensor 1.1.615.1

 

Hello Piotr Randziak.
At the station where I have eseta there is a Direct Cloud Communication Module 1123.1. I still perform at computer stations.

Edited January 11, 2022 by Martino

[Peter Randziak 1,183]

Hello @Martino,

Try to run manual update to get Direct Cloud communication module 1123.2.

Once you have it, try to reboot the system and if the issue will persist after it, enable the Direct Cloud advanced logging, let it run for about 30 minutes, disable the logging and send me the log via a private message to check.

How is the system affected connected to the internet? Wifi, cable or both at the same time?

Regards, Peter

[Martino 1]

Hello Peter:)

The problem was solved by the following:

Troubleshooting

If you get the EPNS service servers are not accessible alert, follow these steps to disable the connection timeout limits:

1.Create a configuration file reqtimeout.conf:
sudo touch /etc/httpd/conf.d/reqtimeout.conf

2.Open the file in a text editor:
nano /etc/httpd/conf.d/reqtimeout.conf

3.Type this setting into the file:
RequestReadTimeout header=0 body=0

4.Save the changes and close the file:
CTRL+X > type Y > press Enter

5.Open the httpd.conf file:
nano /etc/httpd/conf/httpd.conf

6.Add the following line at the end:
IncludeOptional conf.d/reqtimeout.conf

7.Save the changes a close the file:
CTRL+X > type Y > press Enter

8.Restart the Apache HTTP Proxy service:
systemctl restart httpd

after doing the above, everything is green at the stations :).