Another question I have as far as certificates go for pfSense, we use a private IP address for the WAN. When we create the certificates using OpenSSL for Windows, we use the IP address as the Common Name (CN). Should we use the Fully Qualified Domain Name (FQDN) as the CN or is the IP address OK?
Thanks Dwane ________________________________ From: Atkins, Dwane P [mailto:[EMAIL PROTECTED] Sent: Monday, August 20, 2007 4:52 PM To: support@pfsense.com Subject: [pfSense Support] Issues with system->advanced/certification issues. Good afternoon, I just installed 1.2RC2. I wanted to see if our issue was resolved concerning when we have self-signed (or self generated certificates), and we click on System->Advanced, it will conclude every session on the Captive Portal. Personnel have to re-authenticate in order to regain connectivity. These are the scenarios that I performed today and each of them came up with the same error about the webConfigurator certificates have changed. Tried with System->General Setup->webGUI protocol set to http, self-signed certs, System->Advanced-> webGUI SSL, generated from OpenSSL intalled and I received this error Tried with System->General Setup->webGUI protocol set to https, self-signed cert, in System->Advanced-> webGUI SSL, generated from OpenSSL installed and still receive the same error. Tried with System->General Setup->webGUI protocol set to http, no self signed certs in the System->Advanced-> webGUI SSL certificate/key and it does not conclude connectivity on the CaptivePortal. Aug 20 16:33:12 check_reload_status: webConfigurator restart in progress Aug 20 16:33:06 php[1496]: /system_advanced.php: webConfigurator certificates have changed. Restarting webConfigurator. Aug 20 16:31:50 check_reload_status: reloading filter Is there an issue with creating self-signed certificate using OpenSSL and pfSense? Can someone explain the "Create Certificate automatically" link on the System-Advanced- webGUI SSL certificate/key? Thank you all for your help. Dwane <mailto:[EMAIL PROTECTED]>