bink 0 Posted April 4 Share Posted April 4 Heya, when I initiate a wake-up call via the Protect, this call sometimes goes through and then I get the message "the push notification service is not available" for quite some time. If I then wait long enough, the next call goes through. Everything is enabled in the firewall and communication with the ESET servers also works. Therefore a question: does the wake-up call have something like a cooldown? So that you can only use it, for example, every 10 minutes? Greetings from Germany Link to comment Share on other sites More sharing options...
Administrators Marcos 5,308 Posted April 4 Administrators Share Posted April 4 Please try again and let us know if you are still getting the error. Link to comment Share on other sites More sharing options...
bink 0 Posted April 5 Author Share Posted April 5 15 hours ago, Marcos said: Please try again and let us know if you are still getting the error. Yes. I'm still getting the error. Link to comment Share on other sites More sharing options...
bink 0 Posted April 8 Author Share Posted April 8 Are there any news on this topic? Link to comment Share on other sites More sharing options...
Administrators Solution Marcos 5,308 Posted April 8 Administrators Solution Share Posted April 8 While you may occasionally receive an EPNS error, it should not occur always. Moreover, we are working on an ultimate solution so that the errors never occur. Since the error always occurs for you, I assume there will be a communication problem with the EPNS servers, hence I'd recommend raising a support ticket if the issue is not resolved automatically this week. Link to comment Share on other sites More sharing options...
bink 0 Posted April 8 Author Share Posted April 8 42 minutes ago, Marcos said: While you may occasionally receive an EPNS error, it should not occur always. Moreover, we are working on an ultimate solution so that the errors never occur. Since the error always occurs for you, I assume there will be a communication problem with the EPNS servers, hence I'd recommend raising a support ticket if the issue is not resolved automatically this week. Alright, will do. Thank you for the information. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted May 20 ESET Staff Share Posted May 20 As mentioned in previous comments, such error is not expected to happen, especially not for devices, that are already "enrolled" with ESET Push Notification Service (happens automatically after ESET Management Agent is deployed and has network connectivity to the service). Regarding cool-down, there is indeed a limit (around 1 minute), but there is no indication to the user -> device will just not trigger connection to PROTECT more often, i.e. if there are multiple attempts to wake-up device in short period of time, they will be grouped and operation will be delayed. Peter Randziak and bink 2 Link to comment Share on other sites More sharing options...
bink 0 Posted May 21 Author Share Posted May 21 15 hours ago, MartinK said: As mentioned in previous comments, such error is not expected to happen, especially not for devices, that are already "enrolled" with ESET Push Notification Service (happens automatically after ESET Management Agent is deployed and has network connectivity to the service). Regarding cool-down, there is indeed a limit (around 1 minute), but there is no indication to the user -> device will just not trigger connection to PROTECT more often, i.e. if there are multiple attempts to wake-up device in short period of time, they will be grouped and operation will be delayed. Thanks for the clarification. 👍 Link to comment Share on other sites More sharing options...
Recommended Posts