Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
SSL / CentOS 6.9 SSL Issue with Roundcube Webmail
« on: April 20, 2017, 07:02:42 AM »
Hello,
I installed a new install of CWP-PANEL on CentOS 6.9 yesterday and I ran across an issue that I don't know how to fix.
I've been able to install a COMODO SSL Certificate for a Website that's being hosted on my server. (And it works fine using port 443)
However, I'm trying get the same certificate to work properly with Roundcube, however Roundcube is now using port 2096 (SSL) and the server is giving out a self signed SSL cert instead of the one that I've configured using the SSL Manage inside CWP-PANEL.
So, for example the main website works fine. However if I use domain.com/webmail I get a security warning stating the the SSL cert is invalid (self signed instead of the one that I configured) This issue is new apparently in this version of CWP PANEL. I have used an old version in the past and I don't remember having this issue or changing the standard configuration. I just configured the one certificate and it seemed to work. Anyone have any ideas?
Thank You
I installed a new install of CWP-PANEL on CentOS 6.9 yesterday and I ran across an issue that I don't know how to fix.
I've been able to install a COMODO SSL Certificate for a Website that's being hosted on my server. (And it works fine using port 443)
However, I'm trying get the same certificate to work properly with Roundcube, however Roundcube is now using port 2096 (SSL) and the server is giving out a self signed SSL cert instead of the one that I've configured using the SSL Manage inside CWP-PANEL.
So, for example the main website works fine. However if I use domain.com/webmail I get a security warning stating the the SSL cert is invalid (self signed instead of the one that I configured) This issue is new apparently in this version of CWP PANEL. I have used an old version in the past and I don't remember having this issue or changing the standard configuration. I just configured the one certificate and it seemed to work. Anyone have any ideas?
Thank You
Pages: [1]
