Messaging Gateway

I am having a problem accessing the SBG web interface on an 8.0 machine. While I was trying to configure the certificate for the server I selected No Certificate in the interface options by accident instead of selecting the Demo cert.

Now I cannot access the page, does anyone know how I can re-enable the web interface cert by the command line interface?

I have seen a solution for V9 which doesn't work on V8

I have tried to use the help menu in the vmware console but don't know enough about the system to get the access working. I tried using the http on command and rebooted thesystem but still cannot access. I also tried the set-control;-center-port-443 and this didn't allow me access either.

Can someone let me know what I need to do to allow me access to the console so I can reset the certificate setting to Demo Cert?

 

from the CLI

   http ON
   service controlcenter restart

Access the GUI over HTTP://

Remember to issue   http off    once you get the certificate assigned.


From the 8.03 manual:

http
The http command enables or disablesHTTPaccess for your appliance. By default,
each appliance has the HTTPS Web server enabled and the HTTP Web server
disabled. Using the http command has no effect on HTTPS access. After executing
the command, the Control Center must be restarted with the service command
for the change to take effect.
The http command has the following syntax:
http <on|off>
where on enables HTTP access and off disables HTTP access.
Type help http from the appliance for online assistance.

Thanks for the feedback

I mentioned that I had tried that method in my original post. reset the http to ON and restarted the console..... no joy. I get a website found message but then the site never comes up....

Is there something else I need to look at in addition to the Http on cmd?

this is for an 8.0.2 system if that makes a difference......

Sorry,  I'm on 9.x now and never had this issue while on 8.0.2

I'm working on upgrading to 9.x at the moment through the console......... here's hoping.....

OK Upgraded to v9.x BUT

I used the cc-config http --on command

still unable to log on to console

What am I missing?

At this point, I would probably recommend opening a support case with Symantec to do a proper review of your configuration and see how we can reset the settings to access the web interface.

How do I go about doing that? I don't waste hours finding the right person..........

Do you have a number I can call and what is this going to cost me?

I do not know about costs--but this link has explanation on opening up a case with Symantec.

https://www-secure.symantec.com/connect/forums/open-case-symantec

You should be able to escalate fairly quickly. As far as cost, Symantec Brightmail Gateway is sold with a support entitlement (either Basic or Essential), so this shouldn't cost you extra - it should be included in your support entitlement.  The primary distinction is between hours of support (Basic is business hours 5 days a week, Essential is 24x7). 

Hi,

For 8.0.x I'm pretty sure you can run "clear keystore" command over SSH as admin user to reset the UI back to the self signed certificate.
On 9.0 it's "Delete keystore".

HTH

//ian

Ian

Tried the Delete Keystore command

Still unable to connect to the web console

Browser states "website found. waiting for reply...."

as I have reset Http and deleted done keystore delete and still can't access either by http or https to the ip or name of the filter......... could this be a Tomcat issue? Or is there something else to try on the Certificate situation?

Chris

OK. 

What's the actual error returned to the browser after the 'website found. waiting for reply'?

Also you could try http://%YOUR_IP:41443

Failing that, from the console as admin run this:

cat /data/logs/bcc/catalina.out

Hi Ian

I'm in.....

Tried running through the commands again and checked the default ports... now in on HTTP and going to reset the Cert issue.....

However the whole certificate page appears to have changed between 8.x and 9.x....... where do I tell the system to use the Demo cert.... or has this changed?

Hi folks,

Yeh.

It's under:

Administration > Control Centre > Certificates Tab.

Change the drop down to "Demo Certificate".

HTH

//ian

Solving this was a group effort with many thanks to all on this thread. There were a few missteps and things that weren't clear to me in some on-line instructions and KB articles so below is a summary of the steps I took that actually fixed the issue for my particular situation.

First, upgraded the installation to the latest version this was done through the vmware/CLI console access using "update download" to obtain upgrades and  "update install" to do the installation... this was done for each of the upgrades necessary from 8.0.2 through to 9.0.1-10. (a fairly easy process  have to say).



Second, in the vmware/CLI console reset the UI back to the self signed certificate run "delete keystore".



Third, in the vmware/CLI console run "cc-config http --on".



Fourth, use Internet browser browser to access http://<servername/IP>:41080 and log in to the control center.



Fifth,  go to Administration > Control Centre > Certificates Tab. Change the drop down to "Demo Certificate".



Sixth, in the vmware/CLI console run "cc-config http --off"



Seventh, in the vmware/CLI console "run cc-config port-443 --on" (just to be sure.....)



Finally, you can access the control center using a short cut pointing to https://<servername/IP>



Though out this the filter was working fine and all the reports and quarantined messages just where they should be.

Thanks again for everyone's input

For the contest, you can't get credit toward "King of the Week" for your own thread.

None-the-less, thrilled you solved your issue!

Best,

Eric

Ah Well.... the problem is sorted and that's the main thing for me.

When enabling http the steps are actually a bit different than posted earlier.

rom the CLI

   http ON
   service controlcenter restart

Access the GUI over HTTP://<server or IP>:41080

Because while you enable connection to BCC without encryption, port 80 is not enabled.