Hi,

I am unable to use the captive portal with https certificate and custom domain name support.

When we are on the captive portal connection page it uses the IP address of the server on which the controller is hosted.

When customers connect, they get the message "not secure" which does not look professional at all and does not guarantee the security of the data exchange.

• Our controller is hosted on an Ubuntu 22.04 server
• Accessible via a personalized domain name: omada.xxxx-support.xx
• Certification authority: let's encrypt
• https certificate in place and valid on the domain linked to the controller

What are the steps or configuration required to use the captive portal with a custom domain name and a valid https certificate?