Jump to content

Login failed (communication error)


Go to solution Solved by Megachip,

Recommended Posts

Got this error on Web-Console after upgrading from 6.1.28 to 6.1.33. Can't login anymore.
All services running.
Using Appliance and upgrade routine as described here.

 

Suggestions?

 

THX a lot

Edited by Megachip
Link to comment
Share on other sites

I get that sometimes when I try and login. Usually when my session has timed out. I just open a new windows and login. Im sure that is not your issue, but thats my experience.

Link to comment
Share on other sites

  • Former ESET Employees

  • Check ERA Server is running.

Check if it is listening on port 2223.

Try open this port with telnet.

Look at servers trace.log after unsuccessful login, there could be more info what is worng.

Link to comment
Share on other sites

  • Solution

I get that sometimes when I try and login. Usually when my session has timed out. I just open a new windows and login. Im sure that is not your issue, but thats my experience.

Tried several hours from several machines, same error.

  • Check ERA Server is running.
Was running

  • Check if it is listening on port 2223.
  • Try open this port with telnet.
I think it was listing and reachable, but didn't checkt it on Friday.

  • Look at servers trace.log after unsuccessful login, there could be more info what is worng.
No unsuccessful logins in tracelog. Which seems logic for me, cause Web-Console reported communication error.

...

...

Came back from weekend, login works ;)

Edited by Megachip
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...