Jump to content
elaxrocha

Problem logging in ESET Web Console after Update

Recommended Posts

Good afternoon you guys,

So i'm writing in this forum because of a little problem I'm getting with the ESET v7 Web Console.

I updated another machine (with CentOS7), I did the same process and it worked so I don't really know what's the matter.

I had ESET web console and server v6.5 and I updated it to v7 and did the same process that I had done in the other machine but when I try to login with the Administrator account I get an error message "Login Failed: Communication Error", but if i click in "Change Password" and change it I just automatically login after changing.

The problem is that after log out of the Web Console again I get the same error, but if I change the password again I can login, until I log out.

 

I have a CentOS 6.7, TomCat6 and Java 1.8.0_181-b13

 

Edited by elaxrocha

Share this post


Link to post
Share on other sites

[UPDATE]

After trying in another machine with CentOS 6.7, I still get the same error.

I would say the problem here could be the version of my CentOS.

Share this post


Link to post
Share on other sites
Posted (edited)

If I recall correctly, one of my colleagues investigated similar issue (or maybe exactly your in case you filled ESET support ticket?) and problem was with version of Apache Tomcat, where it seems certain security functionality is missing in that version. I would recommend to upgrade if possible, or even better to migrate whole machine to CentOS7, where newer Apache Tomcat is available in official repositories.

Have you tried to log-in without allowing session in multiple tabs (i.e. with disabled checkbox)?

Edited by MartinK

Share this post


Link to post
Share on other sites
On 10/3/2018 at 8:32 PM, MartinK said:

If I recall correctly, one of my colleagues investigated similar issue (or maybe exactly your in case you filled ESET support ticket?) and problem was with version of Apache Tomcat, where it seems certain security functionality is missing in that version. I would recommend to upgrade if possible, or even better to migrate whole machine to CentOS7, where newer Apache Tomcat is available in official repositories.

Have you tried to log-in without allowing session in multiple tabs (i.e. with disabled checkbox)?

Hey,

Thanks for the answer but upgrading TomCat is a very long task, and for upgrading CentOS 6 to 7 there isn't any reliable procedure and it isn't recommended.

So, I was thinking about maybe do a "Pull Database" in a new fresh and clean virtual appliance, but I'm not very sure how the cerificates would work if I do that.

Share this post


Link to post
Share on other sites
24 minutes ago, elaxrocha said:

So, I was thinking about maybe do a "Pull Database" in a new fresh and clean virtual appliance, but I'm not very sure how the cerificates would work if I do that.

Depends on which certificate do you mean:

  • ESMC certificates will be moved to new appliance, i.e. there should ne no problem with AGENT connectivity, as ESMC Server will be using the same certificate as before and CA certificate as available in ESMC Console will be also moved to new appliance
  • ESMC Webconsole certificate won't be preserver, so you will have to repeate steps you made when you deployed custom certificate. Apache Tomcat7 has the same syntax for relevant configuration, so it is just matter of moving certificate file manualy from old appliance to new appliance, and adapt configuration in server.xml.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×