27-01-2026 12:28 PM
Does anyone know why the hub requires switching to https, but then reverts to http. Why does it not have an ssl certificate if it insists on https?
27-01-2026 03:12 PM
Where are you seeing it revert to http? I get the initial redirect/browser override and from there it all looks to be https.
The hub does have a TLS certificate but it's self-signed (thus the browser errors). In theory, there's no reason why it couldn't use a 'proper', publicly-signed certificate but I imagine it would involve either offering the funcitonality for customers to generate and upload their own certs to the hub (can't see that happening), or some sort of management process that silently generates/renews/installs certificates as required for each customer's hub - not impossible, but probably complex/costly.
27-01-2026 04:28 PM - edited 27-01-2026 04:29 PM
When i browse the hub, I get the use https dialogue then the standard dialogues about safety, and proceed anyway. When it the opens the hub web page the https:// is in red, meaning it is not a secure ssl connection
That is what I meant by it reverts to http, basically insecure. There appears to be no certificate, hence my question
So what is the point of forcing the browser to https, only to say its invalid?
28-01-2026 06:46 AM
It shows red as it sees the certificate as invalid, it is still https protocol.
28-01-2026 08:55 AM
Yes you are right. Wonder if I can somehow create a cert.