

Added the Super/Windows key to the toolbar.Fixed an issue where you didn't get scrollbars in your browser on Windows if.New translations for Russian, Korean, Czech and Chinese (traditional) languages.The last release, but the highlights of what's included in this release are: Lots of changes have been made since the last release, but the highlights are:Ī new stable release of noVNC is now available. This made it possible to use more modern features and clean up a large number of workarounds.Ī beta of noVNC 1.3.0 is now available. Support for Internet Explorer has been dropped.Plain authentication passwords now support longer passwords, which can be useful if you're using a password manager.The error displayed in this case was "Error decoding rect: TypeError". Fixed a disconnect that happened when using some VNC servers.Fixed a bug with the Alt key on Firefox.This allows our library to not only react on browser window changes, but to size changes of the screen element as well. Resizes of the viewport are handled in a more modern way.RTCDataChannel is now supported as a communication channel, an alternative to WebSockets.The novnc_proxy command (earlier launch.sh) is now able to interface better towards Websockify and now has it's own man page.Added French and Portuguese (Brazil) translations.Lots of changes have been made since the last release, but the highlights are: I'm not sure how this relates to having a monitor plugged in or not, but the error message you're getting would indicate that the server is failing to start.A stable release of noVNC is now available. We've found a problem with the installed init script for the VNC Server, which seems to be causing a problem on some systems. Hi, I work for RealVNC and have been investigating an issue that a few people have reported where the VNC Server is not starting automatically on boot. Using the default IP, appending :1 or :0, appending the port number. I get the error above with every permutation of port I can think of. This is via my internal network only - the pi's IP is .20. If I reboot with a monitor, I can VNC in every time. Every attempt to log in headless gives me an error: "The connection was refused by the host computer". I can use VNC viewer to access my pi remotely only when I have a monitor attached. I've set up the realvnc server and even created a virtual desktop. Apathos wrote:I've just installed the newest version of NOOBS/Raspbian without issue.
