Messaging Gateway

I cannot login to Brightmail Control Center anymore.
After pushing "Login" my browser shows "Connecting" forever.
It is not a username/password problem. When I use wrong credentials I receive an error immediately.
I can use the console as well.

Anyway the gateway works. Mail are routed normally. I just can't login to the Control Center.
 

Details :

Version 9.5.3 vmAppliance running on vmWare Workstation 8.0.3 under Windows 2008R2.
IE 9 / Firefox 12
 

Hints ? Ideas ?
Thanks for any assistance.

paul

First, I need to preface that this is not supported. We only certify the Messaging Gateway software to work on VMWare's ESX, ESXi, and vSphere products, not Workstation.

That said, can you log into the console using the same credentials?

Just moved from ESXi 5 to Workstation 8. I had the same problem on ESXi.

Login on Console works no problem.
I can give you access if you want.

paul

Since you can log into SSH without issues I suspect that something has happened to the controlcenter service.  You may want to restart the appliance or restart the controlcenter service with the admin account.

You may need to open a support case with the recommendation to run a diagnostics before you open the case.

Sorry, I didn't notice you mention that logging in to the console works fine.

I would recommend a check of the database, done with: cc-config database --repair

If that does not work, I suggest running: delete osconfig

This will reboot the appliance and bring you back to the bootstrap process of asking you to set a password for the admin user, asking for its IP addresses, DNS servers, etc. It does not delete any of your custom policies, mail, quarantine or settings other than the settings it is asking you to re-set.

After "delete osconfig" I was able to login once for let's say 15 seconds. Then the browser said "The connection was reset" and now everything is like before.

I tried that twice.

Any other ideas ? Reinstall ? Can I save policies on console ?

A "cc-config database --repair" after "delete osconfig" helped.

Seems to be OK now. Thanks a lot for your assistance.

paul

I'm glad that worked for you. I gave you the steps in that order since it was most likely some kind of database corruption.