<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hub https in Broadband &amp; Landline</title>
    <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598181#M132931</link>
    <description>&lt;P&gt;Where are you seeing it revert to http? I get the initial redirect/browser override and from there it all looks to be https.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2026 15:12:04 GMT</pubDate>
    <dc:creator>bobpullen</dc:creator>
    <dc:date>2026-01-27T15:12:04Z</dc:date>
    <item>
      <title>Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598136#M132921</link>
      <description>&lt;P&gt;Does anyone know why the hub requires switching to https,&amp;nbsp; but then reverts to http. Why does it not have an ssl certificate if it insists on https?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 12:28:50 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598136#M132921</guid>
      <dc:creator>Pecbeck</dc:creator>
      <dc:date>2026-01-27T12:28:50Z</dc:date>
    </item>
    <item>
      <title>Re: Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598181#M132931</link>
      <description>&lt;P&gt;Where are you seeing it revert to http? I get the initial redirect/browser override and from there it all looks to be https.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 15:12:04 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598181#M132931</guid>
      <dc:creator>bobpullen</dc:creator>
      <dc:date>2026-01-27T15:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598197#M132934</link>
      <description>&lt;P&gt;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&lt;/P&gt;&lt;P&gt;That is what I meant by it reverts to http, basically insecure. There appears to be no certificate, hence my question&lt;/P&gt;&lt;P&gt;So what is the point of forcing the browser to https, only to say its invalid?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 16:29:47 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598197#M132934</guid>
      <dc:creator>Pecbeck</dc:creator>
      <dc:date>2026-01-27T16:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598297#M132953</link>
      <description>&lt;P&gt;It shows red as it sees the certificate as invalid, it is still https protocol.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 06:46:59 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598297#M132953</guid>
      <dc:creator>tnj</dc:creator>
      <dc:date>2026-01-28T06:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598313#M132955</link>
      <description>&lt;P&gt;Yes you are right. Wonder if I can somehow create a cert.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 08:55:57 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1598313#M132955</guid>
      <dc:creator>Pecbeck</dc:creator>
      <dc:date>2026-01-28T08:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: Hub https</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1636561#M143813</link>
      <description>&lt;P&gt;I have configured my laptop to correctly verify the SSL certificate used by my new EE Hub. It appears to use a certificate issued by BT Hub Root&amp;nbsp; CA which is not a public CA.&amp;nbsp; View the certificate details in the browser and you can see the certificate hierarchy.&amp;nbsp; Select the root CA certificate and Export it to a .crt file. If you then import the certificate into the trusted root certificate store using the settings security options the certificate can be verified.&amp;nbsp; &amp;nbsp;However, you may see a different error regarding the certificate common name if you do not use the &lt;A href="https://bthomehub.home" target="_blank"&gt;https://bthomehub.home&lt;/A&gt;&amp;nbsp;address.&amp;nbsp; This can fixed by editing the hosts file and adding 192.168.1.254 bthomehub.home to the file.&amp;nbsp; Hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2026 18:24:20 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Hub-https/m-p/1636561#M143813</guid>
      <dc:creator>rkb12</dc:creator>
      <dc:date>2026-08-25T18:24:20Z</dc:date>
    </item>
  </channel>
</rss>

