Jump to content

badmotorfinger

Members
  • Posts

    10
  • Joined

  • Last visited

Kudos

  1. Upvote
    badmotorfinger gave kudos to MarcFL in Push Notification Service Servers Cannot be Reached...   
    Yes, that's correct. The ESET Push Notification server is having intermittent issues and repair is underway.
  2. Upvote
    badmotorfinger gave kudos to Marcos in Endpoint Security can't connect to Push Notification Service   
    You wrote that you had Endpoint configured to connect through http proxy.
    Please refer to the Troubleshooting section at https://help.eset.com/protect_deploy_va/90/en-US/enable_apache_http_proxy.html:
    If you get the EPNS service servers are not accessible Web Console error, 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 a 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
     
  3. Upvote
    badmotorfinger gave kudos to Marcos in Endpoint Security can't connect to Push Notification Service   
    Then re-configure Apache http proxy as follows:
    1, Either disable the module reqtimeout_module
    2, Or disable limits, ie. by creating a new file reqtimeout.conf in /etc/httpd/conf.d/ and setting "RequestReadTimeout header=0 body=0". Include the file in the configuration, ie. add "IncludeOptional conf.d/reqtimeout.conf" to /etc/httpd/conf/httpd.conf.
×
×
  • Create New...