# Message: Method Not Allowed message when attempting connection to sunstone server with self signed cert **URL:** \ **Category:** Product Support\ **Created:** [October 2, 2015, 8:48pm UTC](https://forum.opennebula.io/t/message-method-not-allowed-message-when-attempting-connection-to-sunstone-server-with-self-signed-cert/1284 "2015-10-02T20:48:09Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![VURoland](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/vuroland/32/7682_2.png) [@VURoland](https://forum.opennebula.io/u/VURoland)\ **Post date:** [October 3, 2015, 9:42pm UTC](https://forum.opennebula.io/t/message-method-not-allowed-message-when-attempting-connection-to-sunstone-server-with-self-signed-cert/1284/2 "2015-10-03T21:42:29Z")
hi Paul, had this before and added this to the test-env. notes: when using a test-environment, so probably a self-signed certificate, you need to get trust for the cert. in your browser. Load the page: [https://yoururl.com:29876](https://yoururl.com:29876) and accept the security risk (especially firefox), afterwards encrypted VNC traffic over the websocket is properly handled and encrypted. A “real” certificate does not need this workaround. Using tcp port 443, and finding a self-signed, non-accepted certificate it will trigger the “create exception” option in a browser. But for secure VNC traffic, using tcp port 29876, it doesnt, so you need to do that manually once, and then it will work as expected (and secure). EDIT: because you post your VNC settings, I assumed you mean encrypted VNC traffic, right ? Accessing Sunstone itself (so not just VNC) is best done using a proxy, like apache or nginx. See this topic for configurations: [VNC with Sunstone behind Nginx Proxy](https://forum.opennebula.io/t/vnc-with-sunstone-behind-nginx-proxy/426) hope this helps! --- _[View the full topic](https://forum.opennebula.io/t/message-method-not-allowed-message-when-attempting-connection-to-sunstone-server-with-self-signed-cert/1284)._