Hi Jae, Thanks for giving me the source commit numbers related to the ikvm feature . But It didn't work after I updated them. Would you like to tell me your github.com/openbmc/openbmc commit number and the target machine of TEMPLATCONF? Best, Xiuzhi Hi xiuzhi, These are my repo information: bmcweb: 9474b3788017bddd70e493e2b9b7674be30abc87 phosphor-webui: 511a2bbc5540fccb883b8d0005c2b387a23c9d05 Cherry picked https://gerrit.openbmc-project.xyz/#/c/openbmc/phosphor-webui/+/10268/ libvncserver: 3348a7e42e86dfb98dd7458ad29def476cf6096f obmc-ikvm: 2bc661d34abd1fda92a9d2b256ed88ca0e90d09a I can see working KVM through https://my.bmc.ip.addr/#/server-control/kvm -Jae On 3/13/2019 7:21 PM, xiuzhi wrote: > Hi Jae, Ed, > I updated the source to openbmc latest version which uses bmcweb > instead of phosphor-rest. > It seemed that ikvm cannot work on bmcweb. > The websit error: > app.bundle.js:43 Refused to connect to 'wss://192.168.200.132/kvm/0' > because it violates the following Content Security Policy directive: > "default-src 'self'". Note that 'connect-src' was not explicitly set, so > 'default-src' is used as a fallback. > Then I modify the bmcweb file include/security_headers_middleware.hpp L40: > // The KVM currently needs to load images from base64 encoded > strings. > // img-src 'self' data: is used to allow that. > // > https://stackoverflow.com/questions/18447970/content-security-policy-data-not-working-for-base64-images-in-chrome-28 > res.addHeader("Content-Security-Policy", > "default-src 'self'; img-src 'self' data:"); > to: > policy-data-not-working-for-base64-images-in-chrome-28 > res.addHeader("Content-Security-Policy", > "script-src 'self'; img-src 'self' data:"); > > The website erro: > "app.bundle.js:43 WebSocket on-error event" > "WebSocket connection to 'wss://192.168.200.132/kvmws' failed: WebSocket > opening handshake timed out" > What is wrong with it? > Best, > Xiuzhi >