Heitor Araujo 0 Posted March 31, 2017 Share Posted March 31, 2017 Hello Eset support! i'm having trouble opening the ESET REMOTE ADMINISTRATOR, i noticed that the "Eset http server" on "services.msc" it's stopped, but i can't get it to start, i will post an screen shot of the error. Help! Link to comment Share on other sites More sharing options...
Administrators Marcos 4,361 Posted April 3, 2017 Administrators Share Posted April 3, 2017 This service is not related to ERA but to the security product that you have installed. Do you have EFSW or Endpoint v6 installed on that machine? Is it configured to create a mirror and provide mirrored update files via http? Link to comment Share on other sites More sharing options...
Heitor Araujo 0 Posted April 3, 2017 Author Share Posted April 3, 2017 The products that i have installed on this server are: ESET File Security Eset Remote Administrator Agent Eset Remote Administrator Server and when i try to log in on ERA, this appears Link to comment Share on other sites More sharing options...
Administrators Marcos 4,361 Posted April 3, 2017 Administrators Share Posted April 3, 2017 The ESET HTTP Server service is a part of EFSW and serves for providing mirrored files via HTTP. If you are having an issue with log in to the web console, it's not related to this service whatsoever. Did you install ERA using the all-in-one ERA installer or you downloaded and installed each component separately? Link to comment Share on other sites More sharing options...
Heitor Araujo 0 Posted April 6, 2017 Author Share Posted April 6, 2017 I installed using the ALL-in-one era! can it be solved without reinstaling the entire server? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 370 Posted April 6, 2017 ESET Staff Share Posted April 6, 2017 (edited) 2 hours ago, Heitor Araujo said: I installed using the ALL-in-one era! can it be solved without reinstaling the entire server? ERA is using Apache Tomcat for hosting WebConsole, but error on screenshot you provided is from Microsoft IIS server. It seems that this service has taken port 443. Seems you have conflicting services running on this machine - and that is something you will have to handle manually as we do no know why this IIS server is running on the same port as Apache Tomcat. Edited April 6, 2017 by MartinK Link to comment Share on other sites More sharing options...
Recommended Posts