Did you configure your server environment too?

System Management, Manage Servers, select your server, SSL fields

No, the SSL fields in System Management, gwava server, are all blank.

I assume I should be able to place the same entry in for the "SSL certificate file" and "SSL key file" and that should take care of the problem after a restart.

Do you know if I need to enter the "SSL pass phrase"?  That field isn't in the Module Manaagement, interfaces, SMTP interface manager.

Yes, do it!

You need a pass phrase if there is one. Therefore I prefer keys without pass phrase - similar to Apache or Nginx environments.

I entered the cert file and the key file information same as in the "Module management, SMTP Interfaces,  SMTP Interface Manager, SSL section.", restarted the server, but no change in the web browser.  If you view the cert from firefox, it still shows the example.com information.

Let's start to check your certificate. Use i.e mxtoolbox for this to check the smtp corner. 

Maybe we are working at the wrong front.

Which fields contain values?

I think I was working in the wrong corner. You are running a rpm version of SMG (this is good!).

However, in this case you have to configure apache!

• apache2 - The web server used to access the web management components of SMG, such as the installation wizard, administration console, and quarantine service.

  Here are some more details:
  https://www.novell.com/documentation/secure-messaging-gateway24.3/secure-messaging-gateway/data/securing_web_ui.html

I don't have a /sites-enabled/ folder.  Should I just place the conf file in /etc/apache2 ?

Also this structure does not exist in my SLES15sp5 smg 24.4 system.

DocumentRoot /opt/gwava/gwavaman/http

Do you know where it should point?

Maybe someone else should step in.

In my environments I use to apache subdirectories conf.d and vhosts.d. I store certs in directory /etc/ssl/servercerts in almost all environments.

But this policy is a very personal one and follows customer rules.

The official apache documentation suggests to use a sites-enabled folder which I never used. So other "knowledge workers" should step in.

Nevertheless, now you know you have to work on apache settings!

Thanks for your quick response and help Diethmar.  I appreciate it.

I think you have me looing int he correctly area now.  There is an /etc/apache2/ssl-global.conf file that has SSL settings that are commented out.  I'll work with that.

Thanks again.

Gene