Making GUI use server's SSL
Posted: 13 Feb 2023, 21:18
Hello,
I have been running a server with the GUI active on ConfigServer Security & Firewall - CSF v14.17 for many years. I currently have a site running on it that has an SSL certificate on it:
https://server.domain.com
When I tell Chrome to view the certificate, I see that it is issued to the common name of server.domain.com and is up to date. It has been using Let's Encrypt and operating for many years.
I currently access the GUI using:
https://server.domain.com:xxxx
However, I get an SSL error in Chrome and always have to tell Chrome to proceed although unsafe, etc. When I tell Chrome to view the certificate, I see that it is issued to the common name of server.domain.com but is an older, expired certificate. So, for some reason, the different port access (as opposed to port 80) is using an old version of the certificate.
I suspect that my issue is caused by my using a different port and possibly need to place another virtual host file. I looked at doing that, but do not know the address of the site, i.e., page that ConfigServer serves up to manage itself.
Am I on the right track? Or is there an easier way to add the GUI page's port to allow it to share the server's SSL?
Thanks for any guidance/help with this!
Charles
I have been running a server with the GUI active on ConfigServer Security & Firewall - CSF v14.17 for many years. I currently have a site running on it that has an SSL certificate on it:
https://server.domain.com
When I tell Chrome to view the certificate, I see that it is issued to the common name of server.domain.com and is up to date. It has been using Let's Encrypt and operating for many years.
I currently access the GUI using:
https://server.domain.com:xxxx
However, I get an SSL error in Chrome and always have to tell Chrome to proceed although unsafe, etc. When I tell Chrome to view the certificate, I see that it is issued to the common name of server.domain.com but is an older, expired certificate. So, for some reason, the different port access (as opposed to port 80) is using an old version of the certificate.
I suspect that my issue is caused by my using a different port and possibly need to place another virtual host file. I looked at doing that, but do not know the address of the site, i.e., page that ConfigServer serves up to manage itself.
Am I on the right track? Or is there an easier way to add the GUI page's port to allow it to share the server's SSL?
Thanks for any guidance/help with this!
Charles