This issue happens because 443 is a privileged port and nova-spiceproxy runs as non-root. Fixing this would probably require us to rethink how this daemon gets deployed, maybe with haproxy (or apache2) in front of it.
@Natalia, I'm marking this bug as a whishlist, if you need this to be higher priority , please share with us the use case that you are trying to satisfy by binding this daemon to the port 443.
This issue happens because 443 is a privileged port and nova-spiceproxy runs as non-root. Fixing this would probably require us to rethink how this daemon gets deployed, maybe with haproxy (or apache2) in front of it.
@Natalia, I'm marking this bug as a whishlist, if you need this to be higher priority , please share with us the use case that you are trying to satisfy by binding this daemon to the port 443.