Get ‘Back to my Pi’ from anywhere with VNC Connect

In today’s guest blog, Andy Clark, Engineering Manager at RealVNC, introduces VNC Connect: a brand-new, and free, version of VNC that makes it simple to connect securely to your Raspberry Pi from anywhere in the world.

Since September 2016, every version of Raspbian has come with the built-in ability to remotely access and control your Raspberry Pi’s screen from another computer, using a technology called VNC. As the original inventors of this technology, RealVNC were happy to partner with Raspberry Pi to provide the community with the latest and most secure version of VNC for free.

We’re always looking to improve things, and one criticism of VNC technology over the years has been its steep learning curve. In particular, you need a bit of networking knowledge in order to connect to a Pi on the same network, and a heck of a lot to get a connection working across the internet!

This is why we developed VNC Connect, a brand-new version of VNC that allows you not only to make direct connections within your own networks, but also to make secure cloud-brokered connections back to your computer from anywhere in the world, with no specialist networking knowledge needed.

I’m delighted to announce that VNC Connect is available for Raspberry Pi, and from today is included in the Raspbian repositories. What’s more, we’ve added some extra features and functionality tailored to the Raspberry Pi community, and it’s all still free for non-commercial and educational use.

‘Back to my Pi’ and direct connections

The main change in VNC Connect is the ability to connect back to your Raspberry Pi from anywhere in the world, from a wide range of devices, without any complex port forwarding or IP addressing configuration. Our cloud service brokers a secure, end-to-end encrypted connection back to your Pi, letting you take control simply and securely from wherever you happen to be.


While this convenience is great for a lot of our standard home users, it’s not enough for the demands of the Raspberry Pi community! The Raspberry Pi is a great educational platform, and gets used in inventive and non-standard ways all the time. So on the Raspberry Pi, you can still make direct TCP connections the way you’ve always done with VNC. This way, you can have complete control over your project and learn all about IP networking if you want, or you can choose the simplicity of a cloud-brokered connection if that’s what you need.

Simpler connection management

Choosing the computer to connect to using VNC has historically been a fiddly process, requiring you to remember IP addresses or hostnames, or use a separate application to keep track of things. With VNC Connect we’ve introduced a new VNC Viewer with a built-in address book and enhanced UI, making it much simpler and quicker to manage your devices and connections. You now have the option of securely saving passwords for frequently used connections, and you can synchronise your entries with other VNC Viewers, making it easier to access your Raspberry Pi from other computers, tablets, or mobile devices.


Direct capture performance improvements

We’ve been working hard to make improvements to the experimental ‘direct capture’ feature of VNC Connect that’s unique to the Raspberry Pi. This feature allows you to see and control applications that render directly to the screen, like Minecraft, omxplayer, or even the terminal. You should find that performance of VNC in direct capture mode has improved, and is much more usable for interactive tasks.


Getting VNC Connect

VNC Connect is available in the Raspbian repositories from today, so running the following commands at a terminal will install it:

sudo apt-get update

sudo apt-get install realvnc-vnc-server realvnc-vnc-viewer

If you’re already running VNC Server or VNC Viewer, the same commands will install the update; then you’ll need to restart it to use the latest version.

There’s more information about getting set up on the RealVNC Raspberry Pi page. If you want to take advantage of the cloud connectivity, you’ll need to sign up for a RealVNC account, and you can do that here too.

Come and see us!

We’ve loved working with the Raspberry Pi Foundation and the community over the past few years, and making VNC Connect available for free on the Raspberry Pi is just the next phase of our ongoing relationship.

We’d love to get your feedback on Twitter, in the forums, or in the comments below. We’ll be at the Raspberry Pi Big Birthday Weekend again this year on 4-5 March in Cambridge, so please come and say hi and let us know how you use VNC Connect!


Michael Horne avatar

That’s brilliant. Thank you to the folks at RealVNC and Raspberry Pi for this – what a great thing to do for free!

Jerry Trickey avatar

Very cool! Thank you for your generosity guys!

LeRoy Rice avatar

Just tried the new version. Much easier and faster. The previous version was so slow and awkward it was of little value so I tried it a few times and abandoned it as a waste of time. Now, with the upgrade, it actually has value. Great job!

Michael Dowman avatar

Much as I hate to be a grump. This isn’t so much free as freemium, as far as I can’t tell. This smells a bit like free advertising for realvnc and I was frustrated that I had to dig further than this blog post to figure that out. Still, the free tier is probably sufficient for most users.

Simon Long avatar

It’s free for personal use; not only that, you would have to pay to get the features which are free on Pi if you wanted to use them on other platforms, so Pi users are getting a good deal thanks to the generosity of RealVNC. Yes, there is an upgraded set of features you can pay for if you want to, but I’ve never needed any of them – the free product is more than sufficient for the average Pi user.

James Hughes avatar

It’s not really free advertising though, is it? RealVNC have spent a load of money making the product work, and work better. And have the provided that work for free (as in beer) to non-commercial Pi users.

Would you begrudge them some advertising for all that work?

Michael Dowman avatar

I don’t begrudge anybody free advertising, especially in an appropriate context such as this. The RealVNC product is fantastic for the average Pi user, and indeed for myself in certain use cases. I would just like a bit more transparency in the blog article because it appears that I am not an average Pi user.

Peter Farrington avatar

That’s awesome. I use VNC with pupils to access RPis on a school network – using both WiFi and direct LAN connection from laptops. We’re fortunate that speed has not been an issue for us. This capability will take projects to the next level. Many thanks, all of you RealVNC folks!

Amelie Schuster avatar

It is an awesome feature that I use daily with several of my RPis. No display, no keyboard etc. needed – still just one click on my Mac to see what they do and how they are. Really great for programming as I can work on my “normal machine” with no difference at all and easily switch from Mac2RPi and back in a millisecond. Great work, keep going.

Jenn Cruz avatar

después de leer bastante documentos sobre el vnc por fin pude conectarla raspberry, lo único que no me ha gustado es que ne la conexión de mi pc no deja ver bien la interfaz, es muy grande los iconos no he podido que quede ajustada a 1024×768

Redd avatar

Sudo raspi-config
Advance Options

Advance Options
Choose Screen Resolution

Chelo avatar

This is awesome! Keep up the good job guys, you rock!

rudy avatar

Anyone already connected the VNC server to the cloudconnect?
After installing and going to the license tab, i do not get the option to sign in. Only a message “allready licensed” and the option to go to the website, do a repair or enter a new license key. Non of the options let me sign in with an account.
Help !

Andy Clark avatar

It sounds like you’re still seeing the older version of VNC. VNC Connect has a white and blue icon.

Try running:

sudo apt-get update

and then following the instructions here:

You will need to restart your VNC Server after installation is complete. The easiest way to do this is to restart your Raspberry Pi

Juha avatar

Can’t get it working. I am getting this from the client:
VNC Server is not licensed correctly.
Connections will be prohibited until a valid license kay is applied.

And looking the raspberry I see:
$ sudo systemctl status vncserver-x11-serviced.service
● vncserver-x11-serviced.service – VNC Server in Service Mode daemon
Loaded: loaded (/usr/lib/systemd/system/vncserver-x11-serviced.service; enabled)
Active: active (running) since ti 2017-02-14 14:49:37 EET; 2 days ago
Main PID: 506 (vncserver-x11-c)
CGroup: /system.slice/vncserver-x11-serviced.service
├─ 506 /usr/bin/vncserver-x11-core -service -pidFile /var/run/…
├─ 724 /usr/bin/vncagent service 18
├─ 995 /usr/bin/vncserverui service 19
└─1034 /usr/bin/vncserverui -statusicon 5

helmi 14 14:49:37 raspberry10 systemd[1]: Started VNC Server in Service Mode daemon.
helmi 14 14:49:38 raspberry10 vncserver-x11[506]: ServerManager: Server started
helmi 14 14:49:38 raspberry10 vncserver-x11[506]: ConsoleDisplay: Cannot find a running X server…vt1
helmi 14 14:49:38 raspberry10 vncserver-x11[506]: AgentInitCheck: agent comms failure
helmi 14 14:49:38 raspberry10 vncserver-x11[506]: ConsoleDisplay: Found running X server (pid=700)
helmi 17 10:16:23 raspberry10 vncserver-x11[506]: FeatureLicensing: No valid license installed.
helmi 17 10:16:57 raspberry10 vncserver-x11[506]: FeatureLicensing: No valid license installed.
helmi 17 10:18:23 raspberry10 systemd[1]: Started VNC Server in Service Mode daemon.
helmi 17 10:19:13 raspberry10 vncserver-x11[506]: FeatureLicensing: No valid license installed.
Hint: Some lines were ellipsized, use -l to show in full.
juha@raspberry10:~ $ ps -ef| grep vnc
root 506 1 0 09:56 ? 00:00:10 /usr/bin/vncserver-x11-core -service -pidFile /var/run/
root 724 1 0 09:56 ? 00:00:00 /usr/bin/vncagent service 18
pi 995 506 0 09:56 ? 00:00:00 /usr/bin/vncserverui service 19
pi 1034 995 0 09:56 ? 00:00:00 /usr/bin/vncserverui -statusicon 5

No idea where to get license.

Juha avatar

ok, it worked after reboot.

SimonFD avatar

Just in case you were wondering why: The key line is “Active: active (running) since ti 2017-02-14 14:49:37 EET; 2 days ago” which is before the new version was installed.

meeego avatar

can this be used over VPN without the cloud platform? i have been accessing my pi with VPN from anywhere in the world already. however, if this also offers performance improvementes over the earlier VNC then I would like to use it over my VPN. not that interested in the cloud that they offer

Andy Clark avatar

Yes, it can. Direct connectivity like you’re already using with your VPN is available alongside cloud connectivity – you can choose whichever works best for you.

Frederic Collin avatar

It works perfectly, and cloud connect is a feature I always wanted for my Pi’s. Encryption is a real plus. Even enabled the memory and CPU footprint is negligeable. All this for free! Big thanks to the Realvnc guys!

Ben Dover avatar

Does sound work with this version?

Andy Clark avatar

I’m afraid not. It’s on our roadmap, but I have no timescales that I can share at the moment.

Pete G avatar

Just a thought, if it can be used with mobile data roaming, I think people should check there data plan costs and usage.

Within WIFI areas seems like a winner.

Steve avatar

This post came along at just the right time, I was about to use a PI as a home security system and was starting to think about remote log in, port forwarding etc.

Installed the latest version last night, set up my security system and have been able to monitor it remotely. Found out my Python script had crashed and restarted it.

Just what I was looking for.

Art Elsea, Jr. avatar

Just installed and it has removed or disabled rdesktop. As I was doing the install, I got this feedback:

“pi@ArtsRPi3-005:~ $ sudo apt-get install realvnc-vnc-server realvnc-vnc-viewer
Reading package lists… Done
Building dependency tree
Reading state information… Done
realvnc-vnc-viewer is already the newest version.
Recommended packages:
The following packages will be REMOVED:
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/5,118 kB of archives.
After this operation, 26.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database … 140117 files and directories currently installed.)
Removing tightvncserver (1.3.9-6.5) …
Processing triggers for man-db ( …
Selecting previously unselected package realvnc-vnc-server.
(Reading database … 140098 files and directories currently installed.)
Preparing to unpack …/realvnc-vnc-server_5.3.2.22607_armhf.deb …
Unpacking realvnc-vnc-server ( …
Processing triggers for gconf2 (3.2.6-3) …
Processing triggers for hicolor-icon-theme (0.13-1) …
Processing triggers for man-db ( …
Processing triggers for gnome-menus (3.13.3-6) …
Processing triggers for desktop-file-utils (0.22-1) …
Processing triggers for mime-support (3.58) …
Processing triggers for shared-mime-info (1.3-1) …
Setting up realvnc-vnc-server ( …
Updating /etc/pam.d/vncserver
Updating /etc/pam.conf… done
Looking for font path… not found.
Original config file “/etc/vnc/config.old” preserved

Installing Raspberry Pi license (VNC Personal)
Please note that this is only valid for non-commercial use on Raspberry Pi devices.
See for further information.
License key has been successfully applied.

Installed systemd unit for VNC Server in Service Mode daemon
Start or stop the service with:
systemctl (start|stop) vncserver-x11-serviced.service
Mark or unmark the service to be started at boot time with:
systemctl (enable|disable) vncserver-x11-serviced.service

Installed systemd unit for VNC Server in Virtual Mode daemon
Start or stop the service with:
systemctl (start|stop) vncserver-virtuald.service
Mark or unmark the service to be started at boot time with:
systemctl (enable|disable) vncserver-virtuald.service

(gconftool-2:24067): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
gconfd-2: no process found”

Now my rdesktop won’t work even on the same LAN.
Apparently, realvnc is incompatible with tightvnc which I believe is required for rdesktop.

Is that the case?



Art Elsea, Jr. avatar

I meant to say

Now my rdesktop won’t work even on the same LAN.
Apparently, realvnc is incompatible with “tightvncserver” which I believe is required for rdesktop.

Is that the case?



Simon Long avatar

“Apparently, realvnc is incompatible with “tightvncserver” which I believe is required for rdesktop. Is that the case?”

Yes, they won’t coexist – if you install realvnc, tightvnc is uninstalled.

fos Greer avatar

I never cease to be amazed. Almost every day there is something else to explore. RealVNC is easy to set up and quite functional through the cloud.

Thanks for the hard work!


Michael avatar

I’ve tried the cloud connect on my T-mobile data and it is a perpetual cycle of “attempting to reconnect” followed by a brief view of the Pi desktop followed by “attempting to reconnect”. I’ve lowered the resolution of the Pi to default 720X480 which slightly increased the amount of desktop that posted before losing connection. Is cloud connect not designed for mobile data? Or is there something else I am missing?

Andy Clark avatar

Cloud connect is designed for mobile data, so what you’re seeing is unexpected. We’ve spotted some issues with iPhones on T-Mobile that are fixed with the latest iOS software update, so it could be that?

Assuming you’re using RealVNC’s VNC Viewer, please get in touch with our support team and we’ll take a look when we’re back in the office next week.

Art Elsea, Jr. avatar

After running:

apt-get remove realvnc-vnc-server realvnc-vnc-viewer


apt install tightvncserver,

rdesktop now works again.

BTW, I am running up to the minute Raspbian Jessie on a Raspberry Pi 3B+

Let me know if there is any way to have both realvnc-vnc-server and tightvncserver running.



Simon Long avatar

“Let me know if there is any way to have both realvnc-vnc-server and tightvncserver running.”

Not as far as I know – it’s one or the other.

Team Lekker Purtsen (Happy Tinker) avatar

We tested this great tool and we made a video of our test:

Paul Sutton avatar


I added the viewer on my mint desktop to /opt so it could be easily added to the menu, given /opt is for optional or additional software.

sudo cp VNC-Viewer-6.0.2-Linux-x64 /opt

It works nicely from the mint menu now.

Hope this helps other users,


Pete G avatar

USEFUL: I was going to install MOSH the alternate to SSH, but I have discovered that its easier to open VNC connect and open a terminal and so bypassing SSH with the dirty cow exploit and the secuity holes associated with MOSH, but also I can leave my terminal open on the PI and return anytime I like to finish the session, which is why I wanted to install MOSH.

Note: iOS needs a bit of tweeking on the iPhone 5S, found it hard to pan around the screen and to many gestures.
But VNC connect is one of my new top 5 for the Raspberry Pi.

solar3000 avatar

Thanks! This is great!

Jim Manley avatar

Of course, the first naughty thing I did was try to install the upgraded RealVNC on the vitrualized x86 Raspbian PIXEL port, but RealVNC isn’t in the repositories for that. I didn’t really expect it to be there, since other very useful ARM/Pi-specific utilities such as raspi-config and the toolbar editor aren’t there, either.

I fully understand the effort required to support the x86 red-haired little bastard stepchild, and the desire to exclusively support the Pi hardware platform with this free version. I also enthusiastically applaud providing the ability to easily and securely access (when requested for support) the many Pii I have gotten into the hands of students and other educators all over the US.

It would be nice, though, for those of us in the educator space who need to do software development for classes on a laptop without an octoPi (TM Moi ;) of cables coming out of a Pi in our laps, strangling us while trying to get work done in transit.

It also eases the fears of fellow and fellowette passengers, aircrews, sky marshals, and TSA inspectors by not having said electronic octoPi (TM Moi ;) splayed out in a carry-on bag or on a tray table. It also aids in clearing the deck to allow eating inedible meals on the rare occasion they’re still offered on longer flights.

No, I don’t routinely work on an OctoPi (TM Moi ;) while driving … I hereby invoke the Bart Simpson Defense: “I didn’t do it. Nobody saw me do it. You can’t prove a thing. Don’t have a cow, man.” ;) There isn’t that much oncoming traffic in the wilds of Wyoming and Montana where I’m often wandering around these days, anyway, other than an occasional bison (buffalo), Bighorn sheep, or mountain goat … although they can all become quite testy when you bug them (aka wandering into their presence) … and then there are the bears and wolves! :D

Andy Clark avatar

Although it’s not in the repositories, you should be able to install the standard VNC Connect on Raspbian x86 by grabbing the DEB x86 packages from our website at

To get everything installed, follow the instructions at

VNC Viewer is exactly the same, and for VNC Server you’ll get the standard set of features ( when running on Raspbian x86, but hopefully it will help.

It’s important to note that we haven’t tested compatibility with bison, sheep or goats (mountain or otherwise), but we are compatible with polar bears: :-)

Jim Manley avatar

My assumption was that the x86 version, and use of the key word and tricky phrase “standard VNC Connect” means it doesn’t have the optimizations and cloud features just released in the Pi ARM Raspbian update. I suppose the x86 version could already be optimized, but my understanding is that it doesn’t provide the free cloud support feature, but I’ll install the current x86 server snd see how things work. If I can use the viewer on any platform to get to any Pi via its server’s cloud feature, that will suffice for everything except when I’m trying to test something rumming on an x86 Raspbian instance through the x86 RealVNC server.

It takes upwards of years to acquire Pii through the educational administrative, acquisition, and IT bureaucracies in numbers sufficient for just one class, let alone all STEM classes that just I teach, and for all STEM classes in just one school? Fuhgeddaboudit! In the meantime, I have to scrounge PCs from piles destined for e-waste so that I can run x86 Raspbian to get things off the ground until Pi hardware can eventually show up. I had been running Debian and other derivatives to get as close to a Raspbian experience as possible.

Anyway, I’ll try everything out in various configurations and report back how it goes and whether there are any other improvements we could really use. In the meantime, keep up the great work and we will appreciatively make great use of what you’ve already done.

Andy Clark avatar

I’m happy to report that cloud connectivity is available on all versions of VNC Connect on Windows, Mac, Linux and Pi, and is free for non-commercial use on those platforms too. has all of the gory details.

Direct connectivity, file transfer, remote printing, signing in with Linux user names and passwords and a couple of other things are all VNC Connect features that are only usually available with paid-for subscriptions, but we’ve made them available for non-commercial or educational use on Raspberry Pi hardware.

We had to do a bit more work with ARM / Raspberry Pi hardware to get the experimental direct capture mode to work, so that is only available on Raspberry Pi hardware.

Oh, and the and the x86 version is already tuned for desktop & server Linux! :-)

Ted avatar

Fantastic. Works well for me! One thing: they reeeeeally want you to use the cloud connection. Had to use google to find more info then click to yet another page to finally see the port used: 5900. So if you forward that on your router, it’s easy enough to connect from outside.

If you forward a different port on your router (but still to port 5900 on the RPi), know that the Viewer uses a single colon for port numbers relative to 5900 or double for absolute port numbers. E.g., either use “yourinternetaddress:10” or “yourinternetaddres::5910”.

Jim Manley avatar

5900 is the “assigned/well-known port” for the VNC protocol in general, not just RealVNC in particular, so you could have fouind it in any VNC documentation and articles on-line in seconds. It’s not a deep, dark, mysterious secret hidden behind a rotating stone wall or on musty library shelves in an Indiana Jones or Da Vinci Code movie :)

Ted avatar

How would I know? And if I knew, how could I be sure they use the standard port? I tried looking it up at their page linked from here, and nothing.

Jim Manley avatar

It seems like you were aware of what a port number is, and using the new-fangled technology called a “WWW search engine”, it wouldn’t take long to do a search for “VNC port number”. Just in case that’s a challenge and you need other port numbers in the future, here’s a link to all of the standard/well-known (aka “system”) and registered port numbers for all of the protocols used over the Internet:

I was a bit inaccurate in that I should have said that 5900 is the _registered_ port number for VNC, not the standard/well-known/system port number (those only exist from 0 through 1023).

Rick avatar

Is there also a possibility to connect via the cloud to a virtual VNC (without knowing the ip)?

Usage example:
A Pi with a kiosk HDMI display. If you change something on it using the terminal, with it not being visible on the HDMI output.

I got the cloud connection and also a virtual vnc working, but not together. I also didn’t find how I could start a virtual VNC at boot.

Andy Clark avatar

Cloud connectivity is only available for the main display, and not virtual VNC Servers I’m afraid.

Steve Martin avatar

are people managing to get past the rCaptcha on the VNC site ? The problem I have is that the page takes so long to load that the site either decies that it can’t load the rCaptcha, or that I am a Robot (no human would wait that long for a page to load).

Steve Martin avatar

The instructions are making no sense to me (coupled with incredibly poor performance from the VNC website and trouble getting past their rCaptcha).

The VNC Website directs you to go the R-Pi VNC Server Licensing, which directs you to the website, which directs you to the R-Pi VNC Server, which directs …. you get the idea.

Andy Clark avatar

Sorry to hear you’ve been having trouble. As you have seen, we’ve been having performance issues with parts of our website today, but I’m told they should now be resolved.

I recommend signing up for an account at, and once you’ve signed up, choose the option to ‘Active a Home subscription’.

You can then enter use the account details you’ve just created into the VNC Server on the Pi, and VNC Viewer on another device to set the two of them up.

Please get in touch with our support team at if things still aren’t working for you, and we’ll see what we can do.

Apologies again.

Steve Martin avatar

This software has just bricked my SD Card.
The combination of trying to run the VNC Server and the browser to do the registration left it maxed out at 100%CPU from which it did not recover after an extended period of time. Eventually I simply had to remove the power. Following which it can no longer boot the card.

Christopher Gioconda avatar

VNC Connect seems to be working correctly on my pi (yay!) but it doesn’t seem that there is a newer version of VNC Viewer for OS X that has the ability to login via VNC Connect. The screen looks nothing like the screenshot from the PC version :(

Andy Clark avatar

How strange! There should be an up to date VNC Connect capable viewer for MacOS 10.10 and later at

If you still have problems, please get in touch with us via

Ed avatar

Could it be that it doesn’t work with the new kernel 4.9 now served by rpi-update? It worked before, and systemctl says it is running, but no vnc server shows up on any port with lsof -i -P. Consequently, the viewer says “connection refused” while trying to connect.

Ed avatar

The Pi I tried this on was headless. I have now connected it to a monitor and I see that, apparently, it is not licensed. I updated and rebooted this Pi quite a few times since this blog came out. The only reason I can think of is that there is a kernel version number check in RealVNC server which “4.4” satisfies and “4.9” fails? As I said, 4.9 is now the latest version installed after using rpi-update.

Ed avatar

For anyone still reading here, yes it doesn’t work with the (currently) newest 4.9 kernel but it’s not a simple version number check; people are aware and apparently working on a fix:

Óscar avatar

Having a freshly installed Pi, I cannot connect to the VNC server with anything at all (except the RealVNC Viewer). No other clients I used work with this server (including the MacOS bundled client “Screen Sharing”), spitting out authentication errors and whatnot.

What gives? Are there any other VNC clients that work with the RealVNC server, or only RealVNC Viewer works?

Marcus avatar

Not sure about your issue, but I use TeamViewer Host to access my Pi, maybe this could work for you as well:

B.K.Jayasundera avatar

Hi Mr Andy Clark,
Thank you for the blog post on RealVNC. Based on your information ,I have prepared a tutorial on controlling Raspberry pi .

B.K.Jayasundera avatar

Hi Marcus
I have used TeamViewer to control Raspberry Pi 3 successfully over the internet.

Andy Wedgbury avatar

Other viewers don’t support RealVNC’s UNIX Password authentication (where you can login using system credentials). If you go to the VNC Server options dialog and change the authentication to “VNC Password” (and set a password), you should then be able to login using any VNC viewer.

Bob S avatar

Got the new version involuntarily by executing ‘sudo rpi-update’. When it starts, it says it is not licensed and a subscription must be purchased. It is not clear that there is a free ‘home’ option. Only after clicking ‘purchase subscription’ then going to the website is it clear there is a free option.

After signing up for the free home version and signing in to VNC Server, it appears that it is ready for connections. However there is still a red X over the icon in the upper right. Restarting the pi shows the same thing. Tried signing in again, and still the message in the ‘Messages’ tab remains. But it looks like connections can be made because on the ‘Connections’ tab, it says, ‘No users are currently connected. Users will be identified as soon as they connect’. Tried connecting from my PC, but it will not connect.

Andy Wedgbury avatar

This is a known issue with RealVNC Server when using the experimental kernel and firmware that is installed when you do rpi-update, see for details.
A fix to the realvnc-vnc-server package is on its way, in the meantime I’d recommend reverting to the stable firmware.

Bob S avatar

I used to be able to connect to the Pi using Remmina Remote Desktop Client from my Ubuntu computer. Is that no longer the case? Must I use the ‘VNC Viewer App’?

Andy Wedgbury avatar

You can use Remmina to make VNC connections to the RealVNC Server, provided you change the authentication type in the VNC Server options to “VNC Password”, and set a password.

You’ll need to use the RealVNC Viewer if you want to take full advantage of the available features (unix password authentication, encryption, cloud connections, remote printing, file transfer).

B.K.Jayasundera avatar

Hi Mr Andy Clark,
Thank you for the blog post on RealVNC. Based on your information ,I have prepared a tutorial on controlling Raspberry pi .

john avatar

Installed Raspbian Jessie Lite.

Want to use raspberry pi as VPN proxy, headless.
Want to be able to SSH to raspberry pi.

But seems I cannot use free version of vnc connect,
if I understand right, it require VNC Server in Virtual Mode, and this is only available in Enterprise mode.
which is not free.

Mattias avatar

Very nice feature, indeed.

If I understand it correctly, the cloud connection still relies on the standard (real)VNC client on the remote (a.k.a. “not at home”) side.

Is it possible to connect the the VNC cloud sollution, using a standard web browser (e.g. Firefox) and standard https port (443) somehow?

Reason is, our firewall at work will allow outgoing connections to standard web http(s) ports 80 and 443 only.

Richard crane avatar

I do a lot of work installing CCTV which requires us to port forward a customers router which is normally done at the time of the installation, however we they default their router or change ISP and get a new router the port forwarding needs to be redone which either needs a site visit or taking control of their desktop pc to access the router.
In some cases this isn’t a problem but by using a Rpi with VNC cloud setup we can send it to them in the post with instructions to plug it into their router and then we can port forward at our leisure, they can then post the pi back when we are done.

M avatar


can I connect to my Pi if it’s connected to Internet via 3G? My laptop (VNCViewer) is connected to separate network via WiFi. Thx

Comments are closed