Bug #14557
closed
SSL Offloading configuration settings missing from frontends
0%
Description
The SSL Offloading section of any and all frontends are missing.
I was expecting to see the section that can be found at 5:25 in this video: https://youtu.be/7WiZ1i2u-Lc?t=326
This section would allow me to select which certificate to use once "SSL Offloading" was selected for an interface on the frontend.
Right now, there is a certificate that gets applied to that interface, however it is a client certificate stored in pfsense's certificate manager! It's not even a server certificate... it's just the very first cert in its certificate store, alphabetically.
Basically, this disallows me from selecting any certificate for my frontend, making SSL functionally unusable on this. I have attached a screenshot showing the lack of configuration option.
Files
| 2023-07-07-01-15-16-Services_ HAProxy_ Frontend_ Edit - protense.admin.andrewcz.com.png (357 KB) 2023-07-07-01-15-16-Services_ HAProxy_ Frontend_ Edit - protense.admin.andrewcz.com.png | Note the lack of SSL Offloading section |
Updated by Andrew Cz about 2 years ago
Andrew Cz wrote:
The SSL Offloading section of any and all frontends are missing.
I was expecting to see the section that can be found at 5:25 in this video: https://youtu.be/7WiZ1i2u-Lc?t=326
This section would allow me to select which certificate to use once "SSL Offloading" was selected for an interface on the frontend.
Right now, there is a certificate that gets applied to that interface, however it is a client certificate stored in pfsense's certificate manager! It's not even a server certificate... it's just the very first cert in its certificate store, alphabetically.
Basically, this disallows me from selecting any certificate for my frontend, making SSL functionally unusable on this. I have attached a screenshot showing the lack of configuration option.
Turns out that a browser extension (Dark Reader) was blocking the toggle of this section when checking the SSL Offload button on the frontend. I'm not sure what changed in either the extension or the javascript, but disabling it for that site works. I can't tell you when it last worked (I had last been tinkering with this maybe back in 2021?) but that resolved it now.
EDIT:
I'm actually ashamed to say that I'm not sure how to close this issue from the GUI, so whoever comes along to close this out; my apologies.
Updated by 