PfSense HAProxy certificate export import

[VMlabman]

@viragomann

Thank you I see where I can do that with in Certificate in pfSense now.

Do I Sign or create keys as CA (root) or intermediate?

On Common Name I Use the FQDN of the device is this right nas.domainname.net ?

On Certificate Type for my devices woul I want to use Server or User

Do I waht to use Alternative Names IP or FQDN if at all would FQDN nas.mydomain.net or domain.net?

I am getting there :-)
Thank you,

[viragomann]

@VMlabman said in PfSense HAProxy certificate export import:

Do I Sign or create keys as CA (root) or intermediate?

You can do either.
I did never create an intermediate on pfSense, however.

On Common Name I Use the FQDN of the device is this right nas.domainname.net ?

Yes.

On Certificate Type for my devices woul I want to use Server or User

A device might almost need a server cert. E.g. for its web server (management interface).

Do I waht to use Alternative Names IP or FQDN if at all would FQDN nas.mydomain.net or domain.net?

With alternative name you can generate SAN certificates for multiple FQDNs and hence multiple devices, or even to include the IP for a device.

[VMlabman]

@viragomann

By add the cert to the local device that will enable me to connect locally via https://nas.domain name.net:443. same as when creating cert. I am asking again to be sure as I am unable to connect. Do I need to add to cert to OS or Browser??

Thanks again next I will include screenshots to see where I am going wrong

[viragomann]

@VMlabman
The browser will complain that the certificate is not issued by a trusted CA out of the box.

The idea was, that you go over HAproxy to your local devices. HAproxy will trust the certs, since it is issued by a CA on pfSense itself.
Also you can disable the cert verification in the backend.

[VMlabman]

@viragomann

Gotcha back to working on HAProxy I’ve had a few problems with it but now we know we got a good Cert from pfSense and CA from pfSense.

Thank you,

[VMlabman]

@viragomann

Now when I am setting up my Front end for the device I get this error also please see screenshots of HAProxy Config are attached.

Errors found while starting haproxy
[NOTICE] (94882) : haproxy version is 2.8.3-86e043a
[NOTICE] (94882) : path to executable is /usr/local/sbin/haproxy
[ALERT] (94882) : config : config: backend 'HPF4AF6E_BE_ipvANY': server 'hpf4af6e' has neither service port nor check port nor tcp_check rule 'connect' with port information.
[ALERT] (94882) : config : Fatal errors found in configuration.

---


[viragomann]

@VMlabman said in PfSense HAProxy certificate export import:

Now when I am setting up my Front end for the device I get this error also please see screenshots of HAProxy Config are attached.

Errors found while starting haproxy
[NOTICE] (94882) : haproxy version is 2.8.3-86e043a
[NOTICE] (94882) : path to executable is /usr/local/sbin/haproxy
[ALERT] (94882) : config : config: backend 'HPF4AF6E_BE_ipvANY': server 'hpf4af6e' has neither service port nor check port nor tcp_check rule 'connect' with port information.
[ALERT] (94882) : config : Fatal errors found in configuration.

The GUI complains that you didn't state a port for the backend server. This is required and cannot be left blank.

Also ensure after correcting this that the backend is shown as online on the StatsFS page.
Since you have set HTTP health check and didn't state a specific URL, it is required that the backend responses to it accordingly at the IP:port.

[VMlabman]

@viragomann

okay I go HAproxy up with not Health Check i had to force it up from teh Stats page. it's still not working

1. Do I have to point in DNS resolver my printer to my HAProxy Server/Firewall?

2. Do I have to set a rule for anything for this wot work if so what would that look like if my HAProxy Server is on 10.50.50.254 and the device it's self is really sitting on 10.50,50.100:443 yet the Front in HAProxp is pointing to LAN address (IPv4) Port 11443. The Backend is pointing to 10.50.50.100 Port 443.

Screenshots provided for review

---

[viragomann]

@VMlabman said in PfSense HAProxy certificate export import:

okay I go HAproxy up with not Health Check i had to force it up from teh Stats page

Basis health check should work well for the most cases and gives a proper feedback if the backend is online.

Do I have to point in DNS resolver my printer to my HAProxy Server/Firewall?

Yes, to an IP, which the frontend is listening on, so LAN in this case.

Do I have to set a rule for anything for this wot work if so what would that look like if my HAProxy Server is on 10.50.50.254 and the device it's self is really sitting on 10.50,50.100:443 yet the Front in HAProxp is pointing to LAN address (IPv4) Port 11443. The Backend is pointing to 10.50.50.100 Port 443.

You just need to allow access on the LAN interface to the LAN IP and port 11443. If you didn't remove the allow-any rule it should work from this point.

Why you're using port 11443 for the frontend at all. This is contrary to the sense of a reverse proxy.

[VMlabman]

@viragomann

1. Backend I changed it to Basic Health Check. Works now

2. Frontend I change it to port 443 ( I was confused as to the port to use ) It's all on 443 now.

1st off Thank you for all your help so far. You have been very kind.

Firewall Rule as I don't 100% understand that part yet. So I am stuck Firewall Rule and i thing I should have it working after that.

Fresh Screenshots w/ Highlighted Changes for reference as of this post

FYI.. This is the YouTube Video I am working from:
link text

---


[VMlabman]

@VMlabman

Here is my interpretation of the Firewall rule

Action: Pass
Interface: LAN
Address Family: IPv4
Protocol: TCP
Source:: LAN address
Destination: LAN subnet
Destination Port Range: HTTPS (443)

---

[viragomann]

@VMlabman said in PfSense HAProxy certificate export import:

Frontend I change it to port 443 ( I was confused as to the port to use ) It's all on 443 now.

443 is the default port for HTTPS. If you use a different one you would have to state it in the URL, e.g. https://nas.local.lan:11443.

A basic idea of a reverse proxy is to share default ports for multiple backends.
This presumes that the single frontend is configured to determine, which backend you want to use. This is mostly achieved by the host header.

When using port 443 for the HAproxy frontend, you have to ensure, that the pfSense web Configurator listens on a different port (443 is default, when enabling HTTPS). It can be changed in System > Advanced > Administration. Doing so you have to state the port in the browser then.

Here is my interpretation of the Firewall rule

What do you want to achieve? I guess, you want your LAN devices to allow access to HAproxy, which is listening on the LAN address.
Hence the source has to be "LAN subnets", the destination "LAN address".

However, out of the box there is an allow-any-to-any rule on LAN:

If you didn't remove or restrict this, it would allow the access to HAproxy already and there would be no need to add an additional rule for it.

[VMlabman]

@viragomann

Hello,

I added the Firewall Rule and I get : ( Warning: Potential Security Risk Ahead )

When I have SSL Offloading Checked on External address in the Frontend. i get:
( Warning: Potential Security Risk Ahead )

When I have SSL Offloading unchecked on External address in the Frontend. i get:
400 Bad Request The plain HTTP request was sent to HTTPS port

I tried to add my NAS device in as a test to see what if might work and I can't get the Backend to start no matter what I set the Health check method to Basic or HTTP. I did come across this digging around on the forums to find there may be an issue with changing the setting in the Backend and having to copy it or re build it. I did both with out a change in the error. I even used a different Frontend to test too. https://forum.netgate.com/topic/182581/may-have-found-a-bug-in-haproxy-using-ssl-backend-ssl-health-check link text

WARNING] (12356) : config : Server Qnap-01_BE_ipvANY/qnap-01 is DOWN, changed from server-state after a reload. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.

I am going to try to re install the package from package manager to see it it fixes anything.

Any suggestions ?

Thank you,

[viragomann]

@VMlabman
In the pfSense GUI or in the browser?
If in the browser, from where?
Something more then this?

[VMlabman]

@viragomann

I will include screenshots as well

On pfSense in HAProxy When I have SSL Offloading Checked on External address in the Frontend. i get: ( Warning: Potential Security Risk Ahead )

When I have SSL Offloading unchecked on External address in the Frontend. i get:
400 Bad Request The plain HTTP request was sent to HTTPS port

[viragomann]

@VMlabman
I guess, your browser is not accepting the SSL certiificate, if SSL is enabled.
Hit the Advanced button to show error details. Also you can show the certificate.

You need to assign a certificate from a trusted CA to the frontend to load the page in the browser without issues.

If you disable SSL, it would be a wrong configuration, so forget this error 400. If the browser tries to connect to https site (port 443) it's expecting to get an SSL certificate.

[VMlabman]

@viragomann

I am using a .wildcard certificate from my pfSense trusted CA to the frontend. I also imported the same Cert into the Printer and NAS. I can create a Cert individually for each of them. I see where in the Edit HAProxy Backend server pool Under Backend I can set a CA: and/or a Client certificate: Shouuld I create the Certs and import them into the devices and list them under the Backend for each host?
Here are some screenshots of the Browser Errors I get in FireFox and Google Chrome. Maybe shis will point at somthing.


[viragomann]

@VMlabman
So this is a self-signed certificate and the browsers will not trust it.
You can install the CA certificate in the browser to trust all certs issued by it. However, you have to do this on each unique browser, which you want to access HAproxy.

In your initial post you wrote that you enable ACME. So my assumption was, that you got a Lets Encrypt certificate to use in HAproxy.
However, you will need a real public domain name to do this.

My suggestion with the local CA was to secure the traffic inside your network. As I wrote above, you can issue (long validity period) certificates from it and install it on your backend devices. So HAproxy can access the backend servers via HTTPS, and will trust the certs, since they issued from a CA on pfSense itself.

[VMlabman]

@viragomann

I am going to go with your suggestion and use HAProxy and pfSence CA's for the few devices. So that is my goal here a Printer and a NAS. I takeing it alittle bit at a time this go at it.

1. Create CA Root in pfSense

2. Create CA Intermediate in PfSense

3. Create / Sign / Export Devise Certs

4. Get Certs onto Devices

5. HAProxy Basic Setup

Thank you,

[VMlabman]

@viragomann

Question when I am creation a Certificate Request from the device and filling in the Common Name Field. Is is case sensitive and is it the FQDN or just the HIOSTNAME?

Thank you,