Jump to content

marlonanjos

Members
  • Content Count

    6
  • Joined

  • Last visited

Profile Information

  • Location
    Brazil
  1. Solved as per @MartinK solution. I added the directive AllowCONNECT 443 80 2222 and also a proxymatch to my ERA Server hostname using the expression generated by https://support.eset.com/en/kb7214-write-a-proxymatch-expression-for-configuration-of-apache-http-proxy-with-esmc-7 to the file /etc/httpd/conf.d/proxy.conf, and restarted the service with systemctl restart httpd After that my agents can connect to my ERA Server through the apache proxy (usually used for updates) and replicate the new policies that removed the wrong settings of using proxy to ERA Server.
  2. @MartinK I tried a simple http/https proxy running on the same host/port and I can see traffic but with 403 code response. I need to do anything more to allow this connection? "CONNECT eraserver:2222 HTTP/1.0" 403 226 "-" "grpc-httpcli/0.0" Also tried to redirect from port 3128(proxy)->2222(era) but failed too.
  3. I mistakenly published a wrong policy with Replication Proxy settings set. Now my agents cant reach our ERA Server to download the new policy without the proxy settings. There is any way to force agents to connect directly to the replication server? Or to reset settings and download new policies like a new install? ERROR: InitializeConnection: Initiating replication connection to 'host: "zzz.zzz.zzz" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "zzz.zzz.zzz" port: 2222 with proxy set as: Proxy: Connection: y
  4. I did not know about the Debug logging. After enabled debug I could see that the problem was with my proxy server. TYVM for your help.
  5. Hi, Im trying to get my Wake-up call to work, but I keep get this error: Error while processing SendWakeUpCall request: Error calling PNS API 'PnsPublish' (return code = 19107) Untranslatable CInterModuleException: Error calling PNS API 'PnsPublish' (return code = 19107) on Agent trace.log the only mentions to wakeup are: EPNS Resource available => initializing Push Notification WakeUp handler PushNotificationWakeUp: registering with EPNS Both server and agent can resolve and reach epns.eset.com on port 8883 and 443 and versions are >7. Thank you in advanc
×
×
  • Create New...