I am using a self-signed certificate. HTTP is working fine, but HTTPS is not.

[goldsoft]

I am using a self-signed certificate. HTTP is working fine, but HTTPS is not. I have set it to allow login without verification and there are no pop-up windows. When using HTTP, it can redirect correctly and everything is normal. However, when using HTTPS, it cannot redirect properly and constantly pops up a log out window. My certificate is the one that comes with PFSENSE.

[Gertjan]

@goldsoft said in I am using a self-signed certificate. HTTP is working fine, but HTTPS is not.:

My certificate is the one that comes with PFSENSE

If you had a web site with a self signed certificate, yo would see the same issue : the browser would complain, as the certificate was signed by 'some one' that isn't on his 'trusted signer list'.
When you visit pfSense GUI using the build in auto generated certicate, you saw the same thing.
Easy solution : import the cert into your web browser cert store, and now its trusted.

The thing is : a captive portal, typically, is used for visitors, and you want them to be able to use your wifi.
With a self signed certificate, they should accept your unsigned cert first, or they have to import the cert .... and this is way to impractical.
If you want to use https : get a domain name, and use that domain name to get a trusted certificate with the help of the pfSense package "acme".

Btw : the https login page is only protecting the login page. As soon as the user is logged in, every site he'll visit on the internet is using https anyway. Mail comes in also over TLS.

I'm using https for my captive portal (a hotel) because its more serious to show
"https://portal.hotel-brand.tld" with a nice padlock an no browser complaints, as a login URL as is "http://192.168.2.1/...."
( Yes, I won (rented) "hotel-brand.tld")

You could do this.