UnRaid's SSL Provisioning and Docker's Interaction with It. Not sure I understand what it benefits.

I was hoping UnRaid's Settings > Management Access > Use SSL/TLS set to "Yes" and Provisioning a Self-signed or user-provided certificate would solve the SSL issue I am having with NextCloud's "Talk" app.

SpaceInvader on Youtube has a video "3 Different Ways to Connect to Unraid over HTTPS." I am opting to try his first method which utilizes the above process. Though this isn't flawless, as clicking on the generated Provisioned URL https://xxx-xxx-xx-xxx following by a long sequence of numbers.myunraid.net gives me a Server Not Found (works for SpaceInvader).

It is documented that NextCloud Talk app has an issue without a "proper" ssl. https://github.com/nextcloud/talk-android/issues/5509

"Since v22.0.0 the talk android app requires every HTTPS certificate to list the server’s name in a special field called the Subject Alternative Name (SAN). Older certificates sometimes listed the server name only in another field called the Common Name (CN). That used to work, but modern systems no longer accept it because it can cause security problems and confusion.

If your certificate does not have a Subject Alternative Name, the app will not trust it, even if the name in the CN looks correct.

Which I indeed get their referenced error, "Error: Hostname example.com not verified"

I have an internal only UnRaid setup as well as all my dockers. I was really hoping UnRaid's SSL/TLS setting would be the solution. Hours I have spent on CA's and other 'solutions' for internal only certificates. None of them seem to work without some domain name needed or external presence.

Do I have the purpose and the intent wrong of this UnRaid Use SSL/TS setting??