[Bug 1259760] Re: Spice console isn't working when ssl_only=True is set

Corey Bryant 1259760 at bugs.launchpad.net
Tue Feb 2 19:03:51 UTC 2021


** Changed in: spice-html5 (Ubuntu)
       Status: Confirmed => Fix Released

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => Fix Released

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: cloud-archive/mitaka
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to spice-html5 in Ubuntu.
https://bugs.launchpad.net/bugs/1259760

Title:
  Spice console isn't working when ssl_only=True is set

Status in OpenStack nova-cloud-controller charm:
  New
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Compute (nova):
  Incomplete
Status in spice-html5 package in Ubuntu:
  Fix Released

Bug description:
  OpenStack instalation: 2013.2
  OS: Ubuntu 13.10
  Repo: standart Ubuntu repozitory

  
  When using ssl_only in nova.conf, browser gets error: 
  [Exception... "The operation is insecure." code: "18" nsresult: "0x80530012 (SecurityError)" location: "https://api.region.domain.tld:6082/spiceconn.js Line: 34"]

  Problem: trying to reach using ws:// schema, not wss://.

  Temporary fixed changing /usr/share/spice-html5/spice_auto.html scheme
  = "wss://" at 82th line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1259760/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list