Certificate covering other ports

[CasN]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
nuy.info
I ran this command:
https://www.nuy.info:4443
It produced this output:
net::ERR_CERT_AUTHORITY_INVALID
My web server is (include version):
apache 2.4.58
The operating system my web server runs on is (include version):
UBUNTU 24.04.1
My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):
Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): partly webmin partly manual

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
2.11.0

My certificate is working properly for my normal website (https://www.nuy.info) however when trying to run my mediaserver over a different port (4443) I get the above message. Is this normal ie can I only resolve that using reverse proxy or did I miss something?

[danb35]

Certificates don't cover ports, they cover domain names. If you have a cert for www.nuy.info, and whatever server software is listening on port 4443 is configured to use that cert, you'll be able to use that without errors. But whatever software is listening on port 4443 is instead using a self-signed cert. You'll need to configure that software, whatever it is, to use your Let's Encrypt cert instead. Or, in the alternative, use a reverse proxy as you've suggested.

[CasN]

Thanks that indeed was the issue. For now I use a normal port untill i figured out how make Subsonic use Letsencrypt.