When you install pfSense, a self-signed SSL certificate is used by default to "secure" the connection to its web interface.
However, as with any self-signed certificate, your web browser will display a security warning each time you access the pfSense web interface.
In this tutorial, you will see how to replace this self-signed SSL certificate with a valid certificate from your certificate authority (CA) installed on Windows Server.
When you try to access the pfSense web interface via Mozilla Firefox, this warning appears: "Warning: Potential Security Risk Ahead".
Click: Advanced.
As Mozilla Firefox tells you, the certificate used by default is self-signed.
Plain Text
The certificate is not trusted because it is self-signed.
Click: View certificate.
As you can see, the subject (who the certificate is intended for) is issued by itself.
Which proves that this certificate is self-signed.
For now, click: Accept the risk and continue.
For the moment, you can see that a triangle appears on the padlock in the address bar.
If you click on it, Mozilla Firefox will tell you "Insecure connection".
Go to: System -> Cert. Manager.
In the "Certificates" tab, you will see that a "webConfigurator default" certificate already exists and that it is self-signed.
To change the hostname and domain used by pfSense, go to: System -> General Setup.
In the "System" section, configure the settings:
Which means that this pfSense machine will be accessible via the FQDN domain name "pfsense.informatiweb.lan" (to be configured manually on your local DNS server).
At the bottom of the page, click Save.
Modifications have been saved.
For this tutorial, we used a local DNS server on Windows Server.
To configure this local DNS server, open DNS Manager and go to your forward lookup zone.
Then right-click "New Host (A or AAAA)".
Note: the certification authority used in our case is a enterprise certification authority installed on Windows Server.
Which requires an Active Directory domain and therefore a local DNS server.
Provide only the host name of your pfSense machine, as well as the IP address of that machine.
Then click: Add host.
Note: the "Create associated pointer (PTR) record" box allows you to create the associated pointer in the reverse lookup zone (if it exists) for reverse DNS resolution (IP to DNS domain name).
The host record has been created.
The DNS record was created in the forward lookup zone.
Same for the pointer (PTR) in the reverse search area (if applicable).
Now that your local domain name is configured for pfSense, navigate to it and again ignore the warning due to the self-signed SSL certificate.
Go to: System -> Cert. Manager.
In the "Certificates" tab, click: Add/Sign.
Choose "Method: Create a Certificate Signing Request" and specify "web interface cert" as the name (Descriptive name).
Enter the fully qualified domain name of your pfSense machine in the "Common Name" box.
In our case: pfsense.informatiweb.lan.
For the Key type and Digest Algorithm to use, leave these as default if you are unsure of what to use.
Indeed, by default, these are the currently recommended values.
The other fields (Country Code, Organization, etc.) are optional and allow you to add information about your company.
In the "Certificates Attributes" section, configure these settings:
Source : Certificate Management - Certificate Settings | pfSense Documentation.
For alternative names, specify:
Then click Save.
Source : Certificate Properties - Subject Alternative Name | pfSense Documentation.
The certificate signing request has been created on your pfSense machine.
Plain Text
Created certificate signing request web interface cert.
Firewall 5/21/2025
Firewall 5/28/2025
Firewall 5/17/2025
Firewall 5/23/2025
Pinned content
Contact
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
You must be logged in to post a comment