> My problem in summary is "*I cannot connect to my broker from a web
> browser using the paho js software without first point the browser to
> the port of my running broker*". This does not seem normal.
When you do visit the WS endpoint first in your browser (using https),
are you getting _any_ certificate warnings (that you then ack)?
If so, that's a problem. Since: WebSocket is a so-called "subresource"
from a browser point of view. That means: the browser will never render
any user dialogs - including "accept invalid cert anyway".
Also: Firefox will allow you do accept "once and for all" an invalid
cert. Chrome not.