BubbleUPNP server Https fails on MacOS Sonoma (14.0)

[Samuel Viana]

Hi,

I upgraded the MacOS runnin on my mac mini M2 to the last release Sonoma. I have the BubbleUpnp Server to launch automatically at startup. THe problem is, after the upgrade, I started to receive complaints on my Phone that it couldn't connect to the Home Proxy. Thougt it was a DNS problem, but my dynamic domain name is correctly assigned to my public IP address. So I went to the mac I thought that the upgrade disabled the startup scripts anyhow, but the BubbleUPNP server was up. I'm running it under OpenJDK 17. Did a netstat and both the ports (http 58050 and https 58051) was up. Then I accessed through the browser the IP in my private network and the http 58050 is ok but the https 58051 is refusing connections. Then finally I tried on localhost 58051 and the browser is giving the  NET::ERR_CERTIFICATE_AUTHORITY_INVALID. So the problem must be related to the root certificates registry  expired in the MacOS upgrade somehow.

[Bubblesoft]

BubbleUPnP Server uses a self-signed certificate, unless you configured it to use your own certificate.

This can make some web browsers to complain about it, but you should be able to allow it to connect:

click the "Advanced" button then "Proceed to connect to localhost". It is safe to connect even if Chrome

goes scary stating otherwise.